Digital assistant providing automated status report

ABSTRACT

Systems and processes for operating a digital assistant are provided. In one example process, a speech input is received from a user. A user intent is determined based on the speech input. Determining the user intent includes generating text based on the speech input, performing natural language processing of the text, and determining the user intent based on a result of the natural language processing. In accordance with the user intent, status information associated with at least one of the one or more electronic devices is requested. The status information associated with the at least one of the one or more electronic devices is received. A spoken output is generated and represents the status information associated with the at least one of the one or more electronic devices. The spoken output is caused to be provided to the user.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to U.S. Provisional Patent ApplicationSer. No. 62/348,660, filed on Jun. 10, 2016, entitled “DIGITAL ASSISTANTPROVIDING AUTOMATED STATUS REPORT,” which is hereby incorporated byreference in its entirety for all purposes.

FIELD

The present disclosure relates generally to a digital assistant and,more specifically, to a digital assistant that provides spoken statusinformation associated with one or more electronic devices.

BACKGROUND

Electronic devices are frequently powered by batteries. Under certaincircumstances, a user may wish to know the battery status of his or herelectronic device. To know the battery status, the user may need to, forexample, take the electronic device out of his or her pocket, activatethe device by pushing a physical button, and look for a battery statusindicator to get the battery status information. This process is oftencumbersome and sometimes not possible if the user is handicapped. It isthus desirable for a device to have the ability to provide spoken statusinformation based on user's speech input.

BRIEF SUMMARY

Some techniques for providing status information require the user tomanipulate a device by hand such that the status information isdisplayed on a display of the user device. The user then looks at thedisplayed status information. Under certain circumstances, displayingthe status information is insufficient or inconvenient for a user. As anexample, if the user is visually impaired or blind, he or she may not beable to look at the battery status indicator on a display. As anotherexample, if the user is busy with other activities (e.g., riding abicycle, driving a car, or playing sports), it would be inconvenient orunsafe for the user to perform a series of steps to obtain the displayedstatus information. In other examples, the devices themselves are, forexample headphones or Bluetooth speakers, are incapable of providing abattery status without connecting to a secondary device, such as a phoneor computer. Some existing speech recognition devices are incapable ofproviding spoken status information, let alone providing spoken statusinformation in response to a user's speech input requesting the statusinformation. Providing a digital assistant that can provide spokenstatus information in response to a user's speech input is thusadvantageous.

Systems and processes for operating a digital assistant are provided. Inaccordance with one or more examples, a method includes, at a userdevice with one or more processors and memory, receiving a speech inputfrom a user. The user device is operable to communicate with one or moreelectronic devices. The method also includes determining a user intentbased on the speech input. Determining the user intent includesgenerating text based on the speech input, performing natural languageprocessing of the text, and determining the user intent based on aresult of the natural language processing. The method further includesrequesting, in accordance with the user intent, status informationassociated with at least one of the one or more electronic devices. Themethod further includes receiving the status information associated withthe at least one of the one or more electronic devices; generating aspoken output representing the status information associated with the atleast one of the one or more electronic devices; and causing the spokenoutput to be provided to the user.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the various described embodiments,reference should be made to the Detailed Description below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1 is a block diagram illustrating a system and environment forimplementing a digital assistant according to various examples.

FIG. 2A is a block diagram illustrating a portable multifunction deviceimplementing the client-side portion of a digital assistant inaccordance with some embodiments.

FIG. 2B is a block diagram illustrating exemplary components for eventhandling according to various examples.

FIG. 3 illustrates a portable multifunction device implementing theclient-side portion of a digital assistant according to variousexamples.

FIG. 4 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface according to various examples.

FIG. 5A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device according to variousexamples.

FIG. 5B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayaccording to various examples.

FIG. 6A illustrates a personal electronic device according to variousexamples.

FIG. 6B is a block diagram illustrating a personal electronic deviceaccording to various examples.

FIG. 7A is a block diagram illustrating a digital assistant system or aserver portion thereof according to various examples.

FIG. 7B illustrates the functions of the digital assistant shown in FIG.7A according to various examples.

FIG. 7C illustrates a portion of an ontology according to variousexamples.

FIGS. 8A-8I illustrate functionality of providing spoken statusinformation by a digital assistant according to various examples.

FIGS. 9A-9B illustrate functionality of providing spoken statusinformation by a digital assistant according to various examples.

FIGS. 10A-10E illustrate functionality of providing spoken statusinformation by a digital assistant according to various examples.

FIGS. 11A-11F illustrates a flow diagram of an exemplary process foroperating a digital assistant according to various examples.

FIG. 12 illustrates a block diagram of an electronic device according tovarious examples.

DETAILED DESCRIPTION

In the following description of the disclosure and embodiments,reference is made to the accompanying drawings, in which it is shown byway of illustration, of specific embodiments that can be practiced. Itis to be understood that other embodiments and examples can be practicedand changes can be made without departing from the scope of thedisclosure.

Techniques for providing spoken status information are desirable. Asdescribed herein, techniques for providing spoken status information ofone or more electronic devices are desired for various purposes such asenabling a visually impaired user to obtain the status information, orenabling a hands-free and/or eye-free operation to obtain the statusinformation. Such techniques are advantageous by allowing the user tooperate a digital assistant using one or more speech inputs and receivespoken status information from the digital assistant. Further, suchtechniques alleviate the cumbersomeness or inconvenience associated withobtaining status information of one or more electronic devices.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first format could be termed a second format,and, similarly, a second format could be termed a first format, withoutdeparting from the scope of the various described examples. The firstformat and the second format can both be formats and, in some cases, canbe separate and different formats.

The terminology used in the description of the various describedexamples herein is for the purpose of describing particular examplesonly and is not intended to be limiting. As used in the description ofthe various described examples and the appended claims, the singularforms “a,” “an,” and “the” are intended to include the plural forms aswell, unless the context clearly indicates otherwise. It will also beunderstood that the term “and/or” as used herein refers to andencompasses any and all possible combinations of one or more of theassociated listed items. It will be further understood that the terms“includes,” “including,” “comprises,” and/or “comprising,” when used inthis specification, specify the presence of stated features, integers,steps, operations, elements, and/or components, but do not preclude thepresence or addition of one or more other features, integers, steps,operations, elements, components, and/or groups thereof.

The term “if” may be construed to mean “when” or “upon” or “in responseto determining” or “in response to detecting,” depending on the context.Similarly, the phrase “if it is determined” or “if [a stated conditionor event] is detected” may be construed to mean “upon determining” or“in response to determining” or “upon detecting [the stated condition orevent]” or “in response to detecting [the stated condition or event],”depending on the context.

1. System and Environment

FIG. 1 illustrates a block diagram of system 100 according to variousexamples. In some examples, system 100 can implement a digitalassistant. The terms “digital assistant,” “virtual assistant,”“intelligent automated assistant,” or “automatic digital assistant” canrefer to any information processing system that interprets naturallanguage input in spoken and/or textual form to infer user intent, andperforms actions based on the inferred user intent. For example, to acton an inferred user intent, the system can perform one or more of thefollowing: identifying a task flow with steps and parameters designed toaccomplish the inferred user intent, inputting specific requirementsfrom the inferred user intent into the task flow; executing the taskflow by invoking programs, methods, services, APIs, or the like; andgenerating output responses to the user in an audible (e.g., speech)and/or visual form.

Specifically, a digital assistant can be capable of accepting a userrequest at least partially in the form of a natural language command,request, statement, narrative, and/or inquiry. Typically, the userrequest can seek either an informational answer or performance of a taskby the digital assistant. A satisfactory response to the user requestcan be a provision of the requested informational answer, a performanceof the requested task, or a combination of the two. For example, a usercan ask the digital assistant a question, such as “Where am I rightnow?” Based on the user's current location, the digital assistant cananswer, “You are in Central Park near the west gate.” The user can alsorequest the performance of a task, for example, “Please invite myfriends to my girlfriend's birthday party next week.” In response, thedigital assistant can acknowledge the request by saying “Yes, rightaway,” and then send a suitable calendar invite on behalf of the user toeach of the user's friends listed in the user's electronic address book.During performance of a requested task, the digital assistant cansometimes interact with the user in a continuous dialogue involvingmultiple exchanges of information over an extended period of time. Thereare numerous other ways of interacting with a digital assistant torequest information or performance of various tasks. In addition toproviding verbal responses and taking programmed actions, the digitalassistant can also provide responses in other visual or audio forms,e.g., as text, alerts, music, videos, animations, etc.

As shown in FIG. 1, in some examples, a digital assistant can beimplemented according to a client-server model. The digital assistantcan include client-side portion 102 (hereafter “DA client 102”) executedon user device 104 and server-side portion 106 (hereafter “DA server106”) executed on server system 108. DA client 102 can communicate withDA server 106 through one or more networks 110. DA client 102 canprovide client-side functionalities such as user-facing input and outputprocessing and communication with DA server 106. DA server 106 canprovide server-side functionalities for any number of DA clients 102each residing on a respective user device 104.

In some examples, DA server 106 can include client-facing I/O interface112, one or more processing modules 114, data and models 116, and I/Ointerface to external services 118. The client-facing I/O interface 112can facilitate the client-facing input and output processing for DAserver 106. One or more processing modules 114 can utilize data andmodels 116 to process speech input and determine the user's intent basedon natural language input. Further, one or more processing modules 114perform task execution based on inferred user intent. In some examples,DA server 106 can communicate with external services 120 throughnetwork(s) 110 for task completion or information acquisition. I/Ointerface to external services 118 can facilitate such communications.

User device 104 can be any suitable electronic device. For example, userdevices can be a portable multifunctional device (e.g., device 200,described below with reference to FIG. 2A), a multifunctional device(e.g., device 400, described below with reference to FIG. 4), or apersonal electronic device (e.g., device 600, described below withreference to FIG. 6A-B.) A portable multifunctional device can be, forexample, a mobile telephone that also contains other functions, such asPDA and/or music player functions. Specific examples of portablemultifunction devices can include the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other examples of portablemultifunction devices can include, without limitation, laptop or tabletcomputers. Further, in some examples, user device 104 can be anon-portable multifunctional device. In particular, user device 104 canbe a desktop computer, a game console, a television, or a televisionset-top box. In some examples, user device 104 can include atouch-sensitive surface (e.g., touch screen displays and/or touchpads).Further, user device 104 can optionally include one or more otherphysical user-interface devices, such as a physical keyboard, a mouse,and/or a joystick. Various examples of electronic devices, such asmultifunctional devices, are described below in greater detail.

Examples of communication network(s) 110 can include local area networks(LAN) and wide area networks (WAN), e.g., the Internet. Communicationnetwork(s) 110 can be implemented using any known network protocol,including various wired or wireless protocols, such as, for example,Ethernet, Universal Serial Bus (USB), FIREWIRE, Global System for MobileCommunications (GSM), Enhanced Data GSM Environment (EDGE), codedivision multiple access (CDMA), time division multiple access (TDMA),Bluetooth, Wi-Fi, voice over Internet Protocol (VoIP), Wi-MAX, or anyother suitable communication protocol.

Server system 108 can be implemented on one or more standalone dataprocessing apparatus or a distributed network of computers. In someexamples, server system 108 can also employ various virtual devicesand/or services of third-party service providers (e.g., third-partycloud service providers) to provide the underlying computing resourcesand/or infrastructure resources of server system 108.

In some examples, user device 104 can communicate with DA server 106 viasecond user device 122. Second user device 122 can be similar oridentical to user device 104. For example, second user device 122 can besimilar to devices 200, 400, or 600 described below with reference toFIGS. 2A, 4, and 6A-B. User device 104 can be configured tocommunicatively couple to second user device 122 via a directcommunication connection, such as Bluetooth, NFC, BTLE, or the like, orvia a wired or wireless network, such as a local Wi-Fi network. In someexamples, second user device 122 can be configured to act as a proxybetween user device 104 and DA server 106. For example, DA client 102 ofuser device 104 can be configured to transmit information (e.g., a userrequest received at user device 104) to DA server 106 via second userdevice 122. DA server 106 can process the information and returnrelevant data (e.g., data content responsive to the user request) touser device 104 via second user device 122.

In some examples, user device 104 can be configured to communicateabbreviated requests for data to second user device 122 to reduce theamount of information transmitted from user device 104. Second userdevice 122 can be configured to determine supplemental information toadd to the abbreviated request to generate a complete request totransmit to DA server 106. This system architecture can advantageouslyallow user device 104 having limited communication capabilities and/orlimited battery power (e.g., a watch or a similar compact electronicdevice) to access services provided by DA server 106 by using seconduser device 122, having greater communication capabilities and/orbattery power (e.g., a mobile phone, laptop computer, tablet computer,or the like), as a proxy to DA server 106. While only two user devices104 and 122 are shown in FIG. 1, it should be appreciated that system100 can include any number and type of user devices configured in thisproxy configuration to communicate with DA server system 106.

Although the digital assistant shown in FIG. 1 can include both aclient-side portion (e.g., DA client 102) and a server-side portion(e.g., DA server 106), in some examples, the functions of a digitalassistant can be implemented as a standalone application installed on auser device. In addition, the divisions of functionalities between theclient and server portions of the digital assistant can vary indifferent implementations. For instance, in some examples, the DA clientcan be a thin-client that provides only user-facing input and outputprocessing functions, and delegates all other functionalities of thedigital assistant to a backend server.

2. Electronic Devices

Attention is now directed toward embodiments of electronic devices forimplementing the client-side portion of a digital assistant. FIG. 2A isa block diagram illustrating portable multifunction device 200 withtouch-sensitive display system 212 in accordance with some embodiments.Touch-sensitive display 212 is sometimes called a “touch screen” forconvenience and is sometimes known as or called a “touch-sensitivedisplay system.” Device 200 includes memory 202 (which optionallyincludes one or more computer-readable storage mediums), memorycontroller 222, one or more processing units (CPUs) 220, peripheralsinterface 218, RF circuitry 208, audio circuitry 210, speaker 211,microphone 213, input/output (I/O) subsystem 206, other input controldevices 216, and external port 224. Device 200 optionally includes oneor more optical sensors 264. Device 200 optionally includes one or morecontact intensity sensors 265 for detecting intensity of contacts ondevice 200 (e.g., a touch-sensitive surface such as touch-sensitivedisplay system 212 of device 200). Device 200 optionally includes one ormore tactile output generators 267 for generating tactile outputs ondevice 200 (e.g., generating tactile outputs on a touch-sensitivesurface such as touch-sensitive display system 212 of device 200 ortouchpad 455 of device 400). These components optionally communicateover one or more communication buses or signal lines 203.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 200 is only one example of aportable multifunction device, and that device 200 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 2A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 202 may include one or more computer-readable storage mediums.The computer-readable storage mediums may be tangible andnon-transitory. Memory 202 may include high-speed random access memoryand may also include non-volatile memory, such as one or more magneticdisk storage devices, flash memory devices, or other non-volatilesolid-state memory devices. Memory controller 222 may control access tomemory 202 by other components of device 200.

In some examples, a non-transitory computer-readable storage medium ofmemory 202 can be used to store instructions (e.g., for performingaspects of process 1200, described below) for use by or in connectionwith an instruction execution system, apparatus, or device, such as acomputer-based system, processor-containing system, or other system thatcan fetch the instructions from the instruction execution system,apparatus, or device and execute the instructions. In other examples,the instructions (e.g., for performing aspects of process 1200,described below) can be stored on a non-transitory computer-readablestorage medium (not shown) of the server system 108 or can be dividedbetween the non-transitory computer-readable storage medium of memory202 and the non-transitory computer-readable storage medium of serversystem 108. In the context of this document, a “non-transitorycomputer-readable storage medium” can be any medium that can contain orstore the program for use by or in connection with the instructionexecution system, apparatus, or device.

Peripherals interface 218 can be used to couple input and outputperipherals of the device to CPU 220 and memory 202. The one or moreprocessors 220 run or execute various software programs and/or sets ofinstructions stored in memory 202 to perform various functions fordevice 200 and to process data. In some embodiments, peripheralsinterface 218, CPU 220, and memory controller 222 may be implemented ona single chip, such as chip 204. In some other embodiments, they may beimplemented on separate chips.

RF (radio frequency) circuitry 208 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 208 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 208 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 208 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 208optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11n,and/or IEEE 802.11ac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 210, speaker 211, and microphone 213 provide an audiointerface between a user and device 200. Audio circuitry 210 receivesaudio data from peripherals interface 218, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 211.Speaker 211 converts the electrical signal to human-audible sound waves.Audio circuitry 210 also receives electrical signals converted bymicrophone 213 from sound waves. Audio circuitry 210 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 218 for processing. Audio data may be retrievedfrom and/or transmitted to memory 202 and/or RF circuitry 208 byperipherals interface 218. In some embodiments, audio circuitry 210 alsoincludes a headset jack (e.g., 312, FIG. 3). The headset jack providesan interface between audio circuitry 210 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 206 couples input/output peripherals on device 200, suchas touch screen 212 and other input control devices 216, to peripheralsinterface 218. I/O subsystem 206 optionally includes display controller256, optical sensor controller 258, intensity sensor controller 259,haptic feedback controller 261, and one or more input controllers 260for other input or control devices. The one or more input controllers260 receive/send electrical signals from/to other input control devices216. The other input control devices 216 optionally include physicalbuttons (e.g., push buttons, rocker buttons, etc.), dials, sliderswitches, joysticks, click wheels, and so forth. In some alternateembodiments, input controller(s) 260 are, optionally, coupled to any (ornone) of the following: a keyboard, an infrared port, a USB port, and apointer device such as a mouse. The one or more buttons (e.g., 308, FIG.3) optionally include an up/down button for volume control of speaker211 and/or microphone 213. The one or more buttons optionally include apush button (e.g., 306, FIG. 3).

A quick press of the push button may disengage a lock of touch screen212 or begin a process that uses gestures on the touch screen to unlockthe device, as described in U.S. patent application Ser. No. 11/322,549,“Unlocking a Device by Performing Gestures on an Unlock Image,” filedDec. 23, 2005, U.S. Pat. No. 7,657,849, which is hereby incorporated byreference in its entirety. A longer press of the push button (e.g., 306)may turn power to device 200 on or off. The user may be able tocustomize a functionality of one or more of the buttons. Touch screen212 is used to implement virtual or soft buttons and one or more softkeyboards.

Touch-sensitive display 212 provides an input interface and an outputinterface between the device and a user. Display controller 256 receivesand/or sends electrical signals from/to touch screen 212. Touch screen212 displays visual output to the user. The visual output may includegraphics, text, icons, video, and any combination thereof (collectivelytermed “graphics”). In some embodiments, some or all of the visualoutput may correspond to user-interface objects.

Touch screen 212 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 212 and display controller 256 (along with anyassociated modules and/or sets of instructions in memory 202) detectcontact (and any movement or breaking of the contact) on touch screen212 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 212. In an exemplaryembodiment, a point of contact between touch screen 212 and the usercorresponds to a finger of the user.

Touch screen 212 may use LCD (liquid crystal display) technology, LPD(light emitting polymer display) technology, or LED (light emittingdiode) technology, although other display technologies may be used inother embodiments. Touch screen 212 and display controller 256 maydetect contact and any movement or breaking thereof using any of aplurality of touch sensing technologies now known or later developed,including but not limited to capacitive, resistive, infrared, andsurface acoustic wave technologies, as well as other proximity sensorarrays or other elements for determining one or more points of contactwith touch screen 212. In an exemplary embodiment, projected mutualcapacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 212 may beanalogous to the multi-touch sensitive touchpads described in thefollowing U.S. Pat. No. 6,323,846 (Westerman et al.), U.S. Pat. No.6,570,557 (Westerman et al.), and/or U.S. Pat. No. 6,677,932(Westerman), and/or U.S. Patent Publication 2002/0015024A1, each ofwhich is hereby incorporated by reference in its entirety. However,touch screen 212 displays visual output from device 200, whereastouch-sensitive touchpads do not provide visual output.

A touch-sensitive display in some embodiments of touch screen 212 may beas described in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005; (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 212 may have a video resolution in excess of 100 dpi. Insome embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user may make contact with touch screen 212using any suitable object or appendage, such as a stylus, a finger, andso forth. In some embodiments, the user interface is designed to workprimarily with finger-based contacts and gestures, which can be lessprecise than stylus-based input due to the larger area of contact of afinger on the touch screen. In some embodiments, the device translatesthe rough finger-based input into a precise pointer/cursor position orcommand for performing the actions desired by the user.

In some embodiments, in addition to the touch screen, device 200 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom touch screen 212 or an extension of the touch-sensitive surfaceformed by the touch screen.

Device 200 also includes power system 262 for powering the variouscomponents. Power system 262 may include a power management system, oneor more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 200 may also include one or more optical sensors 264. FIG. 2Ashows an optical sensor coupled to optical sensor controller 258 in I/Osubsystem 206. Optical sensor 264 may include charge-coupled device(CCD) or complementary metal-oxide semiconductor (CMOS)phototransistors. Optical sensor 264 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module243 (also called a camera module), optical sensor 264 may capture stillimages or video. In some embodiments, an optical sensor is located onthe back of device 200, opposite touch screen display 212 on the frontof the device so that the touch screen display may be used as aviewfinder for still and/or video image acquisition. In someembodiments, an optical sensor is located on the front of the device sothat the user's image may be obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay. In some embodiments, the position of optical sensor 264 can bechanged by the user (e.g., by rotating the lens and the sensor in thedevice housing) so that a single optical sensor 264 may be used alongwith the touch screen display for both video conferencing and stilland/or video image acquisition.

Device 200 optionally also includes one or more contact intensitysensors 265. FIG. 2A shows a contact intensity sensor coupled tointensity sensor controller 259 in I/O subsystem 206. Contact intensitysensor 265 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 265 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 212). In some embodiments, at least one contact intensitysensor is located on the back of device 200, opposite touch screendisplay 212, which is located on the front of device 200.

Device 200 may also include one or more proximity sensors 266. FIG. 2Ashows proximity sensor 266 coupled to peripherals interface 218.Alternately, proximity sensor 266 may be coupled to input controller 260in I/O subsystem 206. Proximity sensor 266 may perform as described inU.S. patent application Ser. No. 11/241,839, “Proximity Detector InHandheld Device”; Ser. No. 11/240,788, “Proximity Detector In HandheldDevice”; Ser. No. 11/620,702, “Using Ambient Light Sensor To AugmentProximity Sensor Output”; Ser. No. 11/586,862, “Automated Response ToAnd Sensing Of User Activity In Portable Devices”; and Ser. No.11/638,251, “Methods And Systems For Automatic Configuration OfPeripherals,” which are hereby incorporated by reference in theirentirety. In some embodiments, the proximity sensor turns off anddisables touch screen 212 when the multifunction device is placed nearthe user's ear (e.g., when the user is making a phone call).

Device 200 optionally also includes one or more tactile outputgenerators 267. FIG. 2A shows a tactile output generator coupled tohaptic feedback controller 261 in I/O subsystem 206. Tactile outputgenerator 267 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 265 receives tactile feedbackgeneration instructions from haptic feedback module 233 and generatestactile outputs on device 200 that are capable of being sensed by a userof device 200. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 212) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 200) or laterally (e.g., back and forth inthe same plane as a surface of device 200). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 200, opposite touch screen display 212, which is located on thefront of device 200.

Device 200 may also include one or more accelerometers 268. FIG. 2Ashows accelerometer 268 coupled to peripherals interface 218.Alternately, accelerometer 268 may be coupled to an input controller 260in I/O subsystem 206. Accelerometer 268 may perform as described in U.S.Patent Publication No. 20050190059, “Acceleration-based Theft DetectionSystem for Portable Electronic Devices,” and U.S. Patent Publication No.20060017692, “Methods And Apparatuses For Operating A Portable DeviceBased On An Accelerometer,” both of which are incorporated by referenceherein in their entirety. In some embodiments, information is displayedon the touch screen display in a portrait view or a landscape view basedon an analysis of data received from the one or more accelerometers.Device 200 optionally includes, in addition to accelerometer(s) 268, amagnetometer (not shown) and a GPS (or GLONASS or other globalnavigation system) receiver (not shown) for obtaining informationconcerning the location and orientation (e.g., portrait or landscape) ofdevice 200.

In some embodiments, the software components stored in memory 202include operating system 226, communication module (or set ofinstructions) 228, contact/motion module (or set of instructions) 230,graphics module (or set of instructions) 232, text input module (or setof instructions) 234, Global Positioning System (GPS) module (or set ofinstructions) 235, Digital Assistant Client Module 229, and applications(or sets of instructions) 236. Further, memory 202 can store data andmodels, such as user data and models 231. Furthermore, in someembodiments, memory 202 (FIG. 2A) or 470 (FIG. 4) stores device/globalinternal state 257, as shown in FIGS. 2A and 4. Device/global internalstate 257 includes one or more of: active application state, indicatingwhich applications, if any, are currently active; display state,indicating what applications, views or other information occupy variousregions of touch screen display 212; sensor state, including informationobtained from the device's various sensors and input control devices216; and location information concerning the device's location and/orattitude.

Operating system 226 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 228 facilitates communication with other devicesover one or more external ports 224 and also includes various softwarecomponents for handling data received by RF circuitry 208 and/orexternal port 224. External port 224 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 230 optionally detects contact with touch screen212 (in conjunction with display controller 256) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 230 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 230 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 230 and display controller 256 detect contact on atouchpad.

In some embodiments, contact/motion module 230 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 200). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 230 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 232 includes various known software components forrendering and displaying graphics on touch screen 212 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 232 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 232 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 256.

Haptic feedback module 233 includes various software components forgenerating instructions used by tactile output generator(s) 267 toproduce tactile outputs at one or more locations on device 200 inresponse to user interactions with device 200.

Text input module 234, which may be a component of graphics module 232,provides soft keyboards for entering text in various applications (e.g.,contacts 237, email 240, IM 241, browser 247, and any other applicationthat needs text input).

GPS module 235 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 238 foruse in location-based dialing; to camera 243 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Digital assistant client module 229 can include various client-sidedigital assistant instructions to provide the client-sidefunctionalities of the digital assistant. For example, digital assistantclient module 229 can be capable of accepting voice input (e.g., speechinput), text input, touch input, and/or gestural input through varioususer interfaces (e.g., microphone 213, accelerometer(s) 268,touch-sensitive display system 212, optical sensor(s) 229, other inputcontrol devices 216, etc.) of portable multifunction device 200. Digitalassistant client module 229 can also be capable of providing output inaudio (e.g., speech output), visual, and/or tactile forms throughvarious output interfaces (e.g., speaker 211, touch-sensitive displaysystem 212, tactile output generator(s) 267, etc.) of portablemultifunction device 200. For example, output can be provided as voice,sound, alerts, text messages, menus, graphics, videos, animations,vibrations, and/or combinations of two or more of the above. Duringoperation, digital assistant client module 229 can communicate with DAserver 106 using RF circuitry 208.

User data and models 231 can include various data associated with theuser (e.g., user-specific vocabulary data, user preference data,user-specified name pronunciations, data from the user's electronicaddress book, to-do lists, shopping lists, etc.) to provide theclient-side functionalities of the digital assistant. Further, user dataand models 231 can includes various models (e.g., speech recognitionmodels, statistical language models, natural language processing models,ontology, task flow models, service models, etc.) for processing userinput and determining user intent.

In some examples, digital assistant client module 229 can utilize thevarious sensors, subsystems, and peripheral devices of portablemultifunction device 200 to gather additional information from thesurrounding environment of the portable multifunction device 200 toestablish a context associated with a user, the current userinteraction, and/or the current user input. In some examples, digitalassistant client module 229 can provide the contextual information or asubset thereof with the user input to DA server 106 to help infer theuser's intent. In some examples, the digital assistant can also use thecontextual information to determine how to prepare and deliver outputsto the user. Contextual information can be referred to as context data.

In some examples, the contextual information that accompanies the userinput can include sensor information, e.g., lighting, ambient noise,ambient temperature, images or videos of the surrounding environment,etc. In some examples, the contextual information can also include thephysical state of the device, e.g., device orientation, device location,device temperature, power level, speed, acceleration, motion patterns,cellular signals strength, etc. In some examples, information related tothe software state of DA server 106, e.g., running processes, installedprograms, past and present network activities, background services,error logs, resources usage, etc., and of portable multifunction device200 can be provided to DA server 106 as contextual informationassociated with a user input.

In some examples, the digital assistant client module 229 canselectively provide information (e.g., user data 231) stored on theportable multifunction device 200 in response to requests from DA server106. In some examples, digital assistant client module 229 can alsoelicit additional input from the user via a natural language dialogue orother user interfaces upon request by DA server 106. Digital assistantclient module 229 can pass the additional input to DA server 106 to helpDA server 106 in intent deduction and/or fulfillment of the user'sintent expressed in the user request.

A more detailed description of a digital assistant is described belowwith reference to FIGS. 7A-C. It should be recognized that digitalassistant client module 229 can include any number of the sub-modules ofdigital assistant module 726 described below.

Applications 236 may include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 237 (sometimes called an address book or contact        list);    -   Telephone module 238;    -   Video conference module 239;    -   Email client module 240;    -   Instant messaging (IM) module 241;    -   Workout support module 242;    -   Camera module 243 for still and/or video images;    -   Image management module 244;    -   Video player module;    -   Music player module;    -   Browser module 247;    -   Calendar module 248;    -   Widget modules 249, which may include one or more of: weather        widget 249-1, stocks widget 249-2, calculator widget 249-3,        alarm clock widget 249-4, dictionary widget 249-5, and other        widgets obtained by the user, as well as user-created widgets        249-6;    -   Widget creator module 250 for making user-created widgets 249-6;    -   Search module 251;    -   Video and music player module 252, which merges video player        module and music player module;    -   Notes module 253;    -   Map module 254; and/or    -   Online video module 255.

Examples of other applications 236 that may be stored in memory 202include other word processing applications, other image editingapplications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, and text input module234, contacts module 237 may be used to manage an address book orcontact list (e.g., stored in application internal state 292 of contactsmodule 237 in memory 202 or memory 470), including: adding name(s) tothe address book; deleting name(s) from the address book; associatingtelephone number(s), email address(es), physical address(es) or otherinformation with a name; associating an image with a name; categorizingand sorting names; providing telephone numbers or email addresses toinitiate and/or facilitate communications by telephone 238, videoconference module 239, email 240, or IM 241; and so forth.

In conjunction with RF circuitry 208, audio circuitry 210, speaker 211,microphone 213, touch screen 212, display controller 256, contact/motionmodule 230, graphics module 232, and text input module 234, telephonemodule 238 may be used to enter a sequence of characters correspondingto a telephone number, access one or more telephone numbers in contactsmodule 237, modify a telephone number that has been entered, dial arespective telephone number, conduct a conversation, and disconnect orhang up when the conversation is completed. As noted above, the wirelesscommunication may use any of a plurality of communications standards,protocols, and technologies.

In conjunction with RF circuitry 208, audio circuitry 210, speaker 211,microphone 213, touch screen 212, display controller 256, optical sensor264, optical sensor controller 258, contact/motion module 230, graphicsmodule 232, text input module 234, contacts module 237, and telephonemodule 238, video conference module 239 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, and textinput module 234, email client module 240 includes executableinstructions to create, send, receive, and manage email in response touser instructions. In conjunction with image management module 244,email client module 240 makes it very easy to create and send emailswith still or video images taken with camera module 243.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, and textinput module 234, the instant messaging module 241 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages may include graphics, photos, audio files, video filesand/or other attachments as are supported in an MMS and/or an EnhancedMessaging Service (EMS). As used herein, “instant messaging” refers toboth telephony-based messages (e.g., messages sent using SMS or MMS) andInternet-based messages (e.g., messages sent using XMPP, SIMPLE, orIMPS).

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, textinput module 234, GPS module 235, map module 254, and music playermodule, workout support module 242 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 212, display controller 256, opticalsensor(s) 264, optical sensor controller 258, contact/motion module 230,graphics module 232, and image management module 244, camera module 243includes executable instructions to capture still images or video(including a video stream) and store them into memory 202, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 202.

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, text input module 234,and camera module 243, image management module 244 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, and textinput module 234, browser module 247 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, textinput module 234, email client module 240, and browser module 247,calendar module 248 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, textinput module 234, and browser module 247, widget modules 249 aremini-applications that may be downloaded and used by a user (e.g.,weather widget 249-1, stocks widget 249-2, calculator widget 249-3,alarm clock widget 249-4, and dictionary widget 249-5) or created by theuser (e.g., user-created widget 249-6). In some embodiments, a widgetincludes an HTML (Hypertext Markup Language) file, a CSS (CascadingStyle Sheets) file, and a JavaScript file. In some embodiments, a widgetincludes an XML (Extensible Markup Language) file and a JavaScript file(e.g., Yahoo! Widgets).

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, textinput module 234, and browser module 247, the widget creator module 250may be used by a user to create widgets (e.g., turning a user-specifiedportion of a web page into a widget).

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, and text input module234, search module 251 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 202 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, audio circuitry 210,speaker 211, RF circuitry 208, and browser module 247, video and musicplayer module 252 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 212 or on an external, connected display via externalport 224). In some embodiments, device 200 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, and text input module234, notes module 253 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 208, touch screen 212, displaycontroller 256, contact/motion module 230, graphics module 232, textinput module 234, GPS module 235, and browser module 247, map module 254may be used to receive, display, modify, and store maps and dataassociated with maps (e.g., driving directions, data on stores and otherpoints of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 212, display controller 256,contact/motion module 230, graphics module 232, audio circuitry 210,speaker 211, RF circuitry 208, text input module 234, email clientmodule 240, and browser module 247, online video module 255 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 224), send an emailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 241, rather than email client module 240, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules may be combined or otherwiserearranged in various embodiments. For example, video player module maybe combined with music player module into a single module (e.g., videoand music player module 252, FIG. 2A). In some embodiments, memory 202may store a subset of the modules and data structures identified above.Furthermore, memory 202 may store additional modules and data structuresnot described above.

In some embodiments, device 200 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device200, the number of physical input control devices (such as push buttons,dials, and the like) on device 200 may be reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 200 to a main, home, or root menu from any userinterface that is displayed on device 200. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 2B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 202 (FIG. 2A) or 470 (FIG. 4) includes event sorter 270 (e.g., inoperating system 226) and a respective application 236-1 (e.g., any ofthe aforementioned applications 237-251, 255, 480-490).

Event sorter 270 receives event information and determines theapplication 236-1 and application view 291 of application 236-1 to whichto deliver the event information. Event sorter 270 includes eventmonitor 271 and event dispatcher module 274. In some embodiments,application 236-1 includes application internal state 292, whichindicates the current application view(s) displayed on touch-sensitivedisplay 212 when the application is active or executing. In someembodiments, device/global internal state 257 is used by event sorter270 to determine which application(s) is (are) currently active, andapplication internal state 292 is used by event sorter 270 to determineapplication views 291 to which to deliver event information.

In some embodiments, application internal state 292 includes additionalinformation, such as one or more of: resume information to be used whenapplication 236-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 236-1, a state queue for enabling the user to go back toa prior state or view of application 236-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 271 receives event information from peripherals interface218. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 212, as part of a multi-touchgesture). Peripherals interface 218 transmits information it receivesfrom I/O subsystem 206 or a sensor, such as proximity sensor 266,accelerometer(s) 268, and/or microphone 213 (through audio circuitry210). Information that peripherals interface 218 receives from I/Osubsystem 206 includes information from touch-sensitive display 212 or atouch-sensitive surface.

In some embodiments, event monitor 271 sends requests to the peripheralsinterface 218 at predetermined intervals. In response, peripheralsinterface 218 transmits event information. In other embodiments,peripherals interface 218 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 270 also includes a hit viewdetermination module 272 and/or an active event recognizer determinationmodule 273.

Hit view determination module 272 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 212 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected may correspond to programmatic levels within aprogrammatic or view hierarchy of the application. For example, thelowest level view in which a touch is detected may be called the hitview, and the set of events that are recognized as proper inputs may bedetermined based, at least in part, on the hit view of the initial touchthat begins a touch-based gesture.

Hit view determination module 272 receives information related to subevents of a touch-based gesture. When an application has multiple viewsorganized in a hierarchy, hit view determination module 272 identifies ahit view as the lowest view in the hierarchy which should handle thesub-event. In most circumstances, the hit view is the lowest level viewin which an initiating sub-event occurs (e.g., the first sub-event inthe sequence of sub-events that form an event or potential event). Oncethe hit view is identified by the hit view determination module 272, thehit view typically receives all sub-events related to the same touch orinput source for which it was identified as the hit view.

Active event recognizer determination module 273 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 273 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 273 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 274 dispatches the event information to an eventrecognizer (e.g., event recognizer 280). In embodiments including activeevent recognizer determination module 273, event dispatcher module 274delivers the event information to an event recognizer determined byactive event recognizer determination module 273. In some embodiments,event dispatcher module 274 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 282.

In some embodiments, operating system 226 includes event sorter 270.Alternatively, application 236-1 includes event sorter 270. In yet otherembodiments, event sorter 270 is a stand-alone module, or a part ofanother module stored in memory 202, such as contact/motion module 230.

In some embodiments, application 236-1 includes a plurality of eventhandlers 290 and one or more application views 291, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 291 of the application 236-1 includes one or more event recognizers280. Typically, a respective application view 291 includes a pluralityof event recognizers 280. In other embodiments, one or more of eventrecognizers 280 are part of a separate module, such as a user interfacekit (not shown) or a higher level object from which application 236-1inherits methods and other properties. In some embodiments, a respectiveevent handler 290 includes one or more of: data updater 276, objectupdater 277, GUI updater 278, and/or event data 279 received from eventsorter 270. Event handler 290 may utilize or call data updater 276,object updater 277, or GUI updater 278 to update the applicationinternal state 292. Alternatively, one or more of the application views291 include one or more respective event handlers 290. Also, in someembodiments, one or more of data updater 276, object updater 277, andGUI updater 278 are included in a respective application view 291.

A respective event recognizer 280 receives event information (e.g.,event data 279) from event sorter 270 and identifies an event from theevent information. Event recognizer 280 includes event receiver 282 andevent comparator 284. In some embodiments, event recognizer 280 alsoincludes at least a subset of: metadata 283, and event deliveryinstructions 288 (which may include sub-event delivery instructions).

Event receiver 282 receives event information from event sorter 270. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation may also include speed and direction of the sub-event. Insome embodiments, events include rotation of the device from oneorientation to another (e.g., from a portrait orientation to a landscapeorientation, or vice versa), and the event information includescorresponding information about the current orientation (also calleddevice attitude) of the device.

Event comparator 284 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 284 includes eventdefinitions 286. Event definitions 286 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(287-1), event 2 (287-2), and others. In some embodiments, sub-events inan event (287) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (287-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (287-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 212, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 290.

In some embodiments, event definition 287 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 284 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 212, when a touch is detected on touch-sensitivedisplay 212, event comparator 284 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 290, the event comparator uses the result of the hit testto determine which event handler 290 should be activated. For example,event comparator 284 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (287) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 280 determines that the series ofsub-events do not match any of the events in event definitions 286, therespective event recognizer 280 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 280 includes metadata283 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 283 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers may interact, or are enabled to interact, with one another.In some embodiments, metadata 283 includes configurable properties,flags, and/or lists that indicate whether sub-events are delivered tovarying levels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 280 activates eventhandler 290 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 280 delivers event information associated with theevent to event handler 290. Activating an event handler 290 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 280 throws a flag associated withthe recognized event, and event handler 290 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 288 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 276 creates and updates data used inapplication 236-1. For example, data updater 276 updates the telephonenumber used in contacts module 237, or stores a video file used in videoplayer module. In some embodiments, object updater 277 creates andupdates objects used in application 236-1. For example, object updater277 creates a new user-interface object or updates the position of auser-interface object. GUI updater 278 updates the GUI. For example, GUIupdater 278 prepares display information and sends it to graphics module232 for display on a touch-sensitive display.

In some embodiments, event handler(s) 290 includes or has access to dataupdater 276, object updater 277, and GUI updater 278. In someembodiments, data updater 276, object updater 277, and GUI updater 278are included in a single module of a respective application 236-1 orapplication view 291. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 200 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs; and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 3 illustrates a portable multifunction device 200 having a touchscreen 212 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 300.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 302 (not drawn to scalein the figure) or one or more styluses 303 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 200. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 200 may also include one or more physical buttons, such as “home”or menu button 304. As described previously, menu button 304 may be usedto navigate to any application 236 in a set of applications that may beexecuted on device 200. Alternatively, in some embodiments, the menubutton is implemented as a soft key in a GUI displayed on touch screen212.

In one embodiment, device 200 includes touch screen 212, menu button304, push button 306 for powering the device on/off and locking thedevice, volume adjustment button(s) 308, subscriber identity module(SIM) card slot 310, headset jack 312, and docking/charging externalport 224. Push button 306 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 200 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 213. Device 200 also, optionally, includes one or morecontact intensity sensors 265 for detecting intensity of contacts ontouch screen 212 and/or one or more tactile output generators 267 forgenerating tactile outputs for a user of device 200.

FIG. 4 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 400 need not be portable. In some embodiments,device 400 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 400 typically includesone or more processing units (CPUs) 410, one or more network or othercommunications interfaces 460, memory 470, and one or more communicationbuses 420 for interconnecting these components. Communication buses 420optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 400 includes input/output (I/O) interface 430 comprising display440, which is typically a touch screen display. I/O interface 430 alsooptionally includes a keyboard and/or mouse (or other pointing device)450 and touchpad 455, tactile output generator 457 for generatingtactile outputs on device 400 (e.g., similar to tactile outputgenerator(s) 267 described above with reference to FIG. 2A), sensors 459(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 265 describedabove with reference to FIG. 2A). Memory 470 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 470 optionally includes one or more storage devicesremotely located from CPU(s) 410. In some embodiments, memory 470 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 202 of portablemultifunction device 200 (FIG. 2A), or a subset thereof. Furthermore,memory 470 optionally stores additional programs, modules, and datastructures not present in memory 202 of portable multifunction device200. For example, memory 470 of device 400 optionally stores drawingmodule 480, presentation module 482, word processing module 484, websitecreation module 486, disk authoring module 488, and/or spreadsheetmodule 490, while memory 202 of portable multifunction device 200 (FIG.2A) optionally does not store these modules.

Each of the above-identified elements in FIG. 4 may be stored in one ormore of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules may be combined or otherwise rearranged invarious embodiments. In some embodiments, memory 470 may store a subsetof the modules and data structures identified above. Furthermore, memory470 may store additional modules and data structures not describedabove.

Attention is now directed towards embodiments of user interfaces thatmay be implemented on, for example, portable multifunction device 200.

FIG. 5A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 200 in accordance withsome embodiments. Similar user interfaces may be implemented on device400. In some embodiments, user interface 500 includes the followingelements, or a subset or superset thereof:

Signal strength indicator(s) 502 for wireless communication(s), such ascellular and Wi-Fi signals;

-   -   Time 504;    -   Bluetooth indicator 505;    -   Battery status indicator 506;    -   Tray 508 with icons for frequently used applications, such as:        -   Icon 516 for telephone module 238, labeled “Phone,” which            optionally includes an indicator 514 of the number of missed            calls or voicemail messages;        -   Icon 518 for email client module 240, labeled “Mail,” which            optionally includes an indicator 510 of the number of unread            emails;        -   Icon 520 for browser module 247, labeled “Browser;” and        -   Icon 522 for video and music player module 252, also            referred to as iPod (trademark of Apple Inc.) module 252,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 524 for IM module 241, labeled “Messages;”        -   Icon 526 for calendar module 248, labeled “Calendar;”        -   Icon 528 for image management module 244, labeled “Photos;”        -   Icon 530 for camera module 243, labeled “Camera;”        -   Icon 532 for online video module 255, labeled “Online            Video;”        -   Icon 534 for stocks widget 249-2, labeled “Stocks;”        -   Icon 536 for map module 254, labeled “Maps;”        -   Icon 538 for weather widget 249-1, labeled “Weather;”        -   Icon 540 for alarm clock widget 249-4, labeled “Clock;”        -   Icon 542 for workout support module 242, labeled “Workout            Support;”        -   Icon 544 for notes module 253, labeled “Notes;” and        -   Icon 546 for a settings application or module, labeled            “Settings,” which provides access to settings for device 200            and its various applications 236.

It should be noted that the icon labels illustrated in FIG. 5A aremerely exemplary. For example, icon 522 for video and music playermodule 252 may optionally be labeled “Music” or “Music Player.” Otherlabels are, optionally, used for various application icons. In someembodiments, a label for a respective application icon includes a nameof an application corresponding to the respective application icon. Insome embodiments, a label for a particular application icon is distinctfrom a name of an application corresponding to the particularapplication icon.

FIG. 5B illustrates an exemplary user interface on a device (e.g.,device 400, FIG. 4) with a touch-sensitive surface 551 (e.g., a tabletor touchpad 455, FIG. 4) that is separate from the display 550 (e.g.,touch screen display 212). Device 400 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 457) fordetecting intensity of contacts on touch-sensitive surface 551 and/orone or more tactile output generators 459 for generating tactile outputsfor a user of device 400.

Although some of the examples which follow will be given with referenceto inputs on touch screen display 212 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 5B. In some embodiments, the touch-sensitive surface(e.g., 551 in FIG. 5B) has a primary axis (e.g., 552 in FIG. 5B) thatcorresponds to a primary axis (e.g., 553 in FIG. 5B) on the display(e.g., 550). In accordance with these embodiments, the device detectscontacts (e.g., 560 and 562 in FIG. 5B) with the touch-sensitive surface551 at locations that correspond to respective locations on the display(e.g., in FIG. 5B, 560 corresponds to 568 and 562 corresponds to 570).In this way, user inputs (e.g., contacts 560 and 562, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,551 in FIG. 5B) are used by the device to manipulate the user interfaceon the display (e.g., 550 in FIG. 5B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 6A illustrates exemplary personal electronic device 600. Device 600includes body 602. In some embodiments, device 600 can include some orall of the features described with respect to devices 200 and 400 (e.g.,FIGS. 2A-4B). In some embodiments, device 600 has touch-sensitivedisplay screen 604, hereafter touch screen 604. Alternatively, or inaddition to touch screen 604, device 600 has a display and atouch-sensitive surface. As with devices 200 and 400, in someembodiments, touch screen 604 (or the touch-sensitive surface) may haveone or more intensity sensors for detecting intensity of contacts (e.g.,touches) being applied. The one or more intensity sensors of touchscreen 604 (or the touch-sensitive surface) can provide output data thatrepresents the intensity of touches. The user interface of device 600can respond to touches based on their intensity, meaning that touches ofdifferent intensities can invoke different user interface operations ondevice 600.

Techniques for detecting and processing touch intensity may be found,for example, in related applications: International Patent ApplicationSerial No. PCT/US2013/040061, titled “Device, Method, and Graphical UserInterface for Displaying User Interface Objects Corresponding to anApplication,” filed May 8, 2013, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, each of which is herebyincorporated by reference in their entirety.

In some embodiments, device 600 has one or more input mechanisms 606 and608. Input mechanisms 606 and 608, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 600 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 600 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms may permit device 600 to be worn by a user.

FIG. 6B depicts exemplary personal electronic device 600. In someembodiments, device 600 can include some or all of the componentsdescribed with respect to FIGS. 2A, 2B, and 4. Device 600 has bus 612that operatively couples I/O section 614 with one or more computerprocessors 616 and memory 618. I/O section 614 can be connected todisplay 604, which can have touch-sensitive component 622 and,optionally, touch-intensity sensitive component 624. In addition, I/Osection 614 can be connected with communication unit 630 for receivingapplication and operating system data, using Wi-Fi, Bluetooth, nearfield communication (NFC), cellular, and/or other wireless communicationtechniques. Device 600 can include input mechanisms 606 and/or 608.Input mechanism 606 may be a rotatable input device or a depressible androtatable input device, for example. Input mechanism 608 may be abutton, in some examples.

Input mechanism 608 may be a microphone, in some examples. Personalelectronic device 600 can include various sensors, such as GPS sensor632, accelerometer 634, directional sensor 640 (e.g., compass),gyroscope 636, motion sensor 638, and/or a combination thereof, all ofwhich can be operatively connected to I/O section 614.

Memory 618 of personal electronic device 600 can be a non-transitorycomputer-readable storage medium, for storing computer-executableinstructions, which, when executed by one or more computer processors616, for example, can cause the computer processors to perform thetechniques described below, including process 1200 (FIGS. 12A-D). Thecomputer-executable instructions can also be stored and/or transportedwithin any non-transitory computer-readable storage medium for use by orin connection with an instruction execution system, apparatus, ordevice, such as a computer-based system, processor-containing system, orother system that can fetch the instructions from the instructionexecution system, apparatus, or device and execute the instructions.Personal electronic device 600 is not limited to the components andconfiguration of FIG. 6B, but can include other or additional componentsin multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that may be displayed on the displayscreen of devices 200, 400, and/or 600 (FIGS. 2, 4, and 6). For example,an image (e.g., icon), a button, and text (e.g., link) may eachconstitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 455 in FIG. 4 or touch-sensitive surface 551 in FIG. 5B)while the cursor is over a particular user interface element (e.g., abutton, window, slider or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 212 in FIG. 2A or touch screen 212in FIG. 5A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionallybased on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholds mayinclude a first intensity threshold and a second intensity threshold. Inthis example, a contact with a characteristic intensity that does notexceed the first threshold results in a first operation, a contact witha characteristic intensity that exceeds the first intensity thresholdand does not exceed the second intensity threshold results in a secondoperation, and a contact with a characteristic intensity that exceedsthe second threshold results in a third operation. In some embodiments,a comparison between the characteristic intensity and one or morethresholds is used to determine whether or not to perform one or moreoperations (e.g., whether to perform a respective operation or forgoperforming the respective operation) rather than being used to determinewhether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface may receive a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location may be basedon only a portion of the continuous swipe contact, and not the entireswipe contact (e.g., only the portion of the swipe contact at the endlocation). In some embodiments, a smoothing algorithm may be applied tothe intensities of the swipe contact prior to determining thecharacteristic intensity of the contact. For example, the smoothingalgorithm optionally includes one or more of: an unweightedsliding-average smoothing algorithm, a triangular smoothing algorithm, amedian filter smoothing algorithm, and/or an exponential smoothingalgorithm. In some circumstances, these smoothing algorithms eliminatenarrow spikes or dips in the intensities of the swipe contact forpurposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface may becharacterized relative to one or more intensity thresholds, such as acontact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

3. Digital Assistant System

FIG. 7A illustrates a block diagram of digital assistant system 700 inaccordance with various examples. In some examples, digital assistantsystem 700 can be implemented on a standalone computer system. In someexamples, digital assistant system 700 can be distributed acrossmultiple computers. In some examples, some of the modules and functionsof the digital assistant can be divided into a server portion and aclient portion, where the client portion resides on one or more userdevices (e.g., devices 104, 122, 200, 400, or 600) and communicates withthe server portion (e.g., server system 108) through one or morenetworks, e.g., as shown in FIG. 1. In some examples, digital assistantsystem 700 can be an implementation of server system 108 (and/or DAserver 106) shown in FIG. 1. It should be noted that digital assistantsystem 700 is only one example of a digital assistant system, and thatdigital assistant system 700 can have more or fewer components thanshown, may combine two or more components, or may have a differentconfiguration or arrangement of the components. The various componentsshown in FIG. 7A can be implemented in hardware, software instructionsfor execution by one or more processors, firmware, including one or moresignal processing and/or application specific integrated circuits, or acombination thereof.

Digital assistant system 700 can include memory 702, one or moreprocessors 704, input/output (I/O) interface 706, and networkcommunications interface 708. These components can communicate with oneanother over one or more communication buses or signal lines 710.

In some examples, memory 702 can include a non-transitorycomputer-readable medium, such as high-speed random access memory and/ora non-volatile computer-readable storage medium (e.g., one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices).

In some examples, I/O interface 706 can couple input/output devices 716of digital assistant system 700, such as displays, keyboards, touchscreens, and microphones, to user interface module 722. I/O interface706, in conjunction with user interface module 722, can receive userinputs (e.g., voice input, keyboard inputs, touch inputs, etc.) andprocesses them accordingly. In some examples, e.g., when the digitalassistant is implemented on a standalone user device, digital assistantsystem 700 can include any of the components and I/O communicationinterfaces described with respect to devices 200, 400, or 600 in FIGS.2A, 4, 6A-B, respectively. In some examples, digital assistant system700 can represent the server portion of a digital assistantimplementation, and can interact with the user through a client-sideportion residing on a user device (e.g., devices 104, 200, 400, or 600).

In some examples, the network communications interface 708 can includewired communication port(s) 712 and/or wireless transmission andreception circuitry 714. The wired communication port(s) can receive andsend communication signals via one or more wired interfaces, e.g.,Ethernet, Universal Serial Bus (USB), FIREWIRE, etc. The wirelesscircuitry 714 can receive and send RF signals and/or optical signalsfrom/to communications networks and other communications devices. Thewireless communications can use any of a plurality of communicationsstandards, protocols, and technologies, such as GSM, EDGE, CDMA, TDMA,Bluetooth, Wi-Fi, VoIP, Wi-MAX, or any other suitable communicationprotocol. Network communications interface 708 can enable communicationbetween digital assistant system 700 with networks, such as theInternet, an intranet, and/or a wireless network, such as a cellulartelephone network, a wireless local area network (LAN), and/or ametropolitan area network (MAN), and other devices.

In some examples, memory 702, or the computer-readable storage media ofmemory 702, can store programs, modules, instructions, and datastructures including all or a subset of: operating system 718,communications module 720, user interface module 722, one or moreapplications 724, and digital assistant module 726. In particular,memory 702, or the computer-readable storage media of memory 702, canstore instructions for performing process 1200, described below. One ormore processors 704 can execute these programs, modules, andinstructions, and reads/writes from/to the data structures.

Operating system 718 (e.g., Darwin, RTXC, LINUX, UNIX, iOS, OS X,WINDOWS, or an embedded operating system such as VxWorks) can includevarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communications between varioushardware, firmware, and software components.

Communications module 720 can facilitate communications between digitalassistant system 700 with other devices over network communicationsinterface 708. For example, communications module 720 can communicatewith RF circuitry 208 of electronic devices such as devices 200, 400,and 600 shown in FIG. 2A, 4, 6A-B, respectively. Communications module720 can also include various components for handling data received bywireless circuitry 714 and/or wired communications port 712.

User interface module 722 can receive commands and/or inputs from a uservia I/O interface 706 (e.g., from a keyboard, touch screen, pointingdevice, controller, and/or microphone), and generate user interfaceobjects on a display. User interface module 722 can also prepare anddeliver outputs (e.g., speech, sound, animation, text, icons,vibrations, haptic feedback, light, etc.) to the user via the I/Ointerface 706 (e.g., through displays, audio channels, speakers,touch-pads, etc.).

Applications 724 can include programs and/or modules that are configuredto be executed by one or more processors 704. For example, if thedigital assistant system is implemented on a standalone user device,applications 724 can include user applications, such as games, acalendar application, a navigation application, or an email application.If digital assistant system 700 is implemented on a server, applications724 can include resource management applications, diagnosticapplications, or scheduling applications, for example.

Memory 702 can also store digital assistant module 726 (or the serverportion of a digital assistant). In some examples, digital assistantmodule 726 can include the following sub-modules, or a subset orsuperset thereof: input/output processing module 728, speech-to-text(STT) processing module 730, natural language processing module 732,dialogue flow processing module 734, task flow processing module 736,service processing module 738, and speech synthesis module 740. Each ofthese modules can have access to one or more of the following systems ordata and models of the digital assistant module 726, or a subset orsuperset thereof: ontology 760, vocabulary index 744, user data 748,task flow models 754, service models 756, and ASR systems.

In some examples, using the processing modules, data, and modelsimplemented in digital assistant module 726, the digital assistant canperform at least some of the following: converting speech input intotext; identifying a user's intent expressed in a natural language inputreceived from the user; actively eliciting and obtaining informationneeded to fully infer the user's intent (e.g., by disambiguating words,games, intentions, etc.); determining the task flow for fulfilling theinferred intent; and executing the task flow to fulfill the inferredintent.

In some examples, as shown in FIG. 7B, I/O processing module 728 caninteract with the user through I/O devices 716 in FIG. 7A or with a userdevice (e.g., devices 104, 200, 400, or 600) through networkcommunications interface 708 in FIG. 7A to obtain user input (e.g., aspeech input) and to provide responses (e.g., as speech outputs) to theuser input. I/O processing module 728 can optionally obtain contextualinformation associated with the user input from the user device, alongwith or shortly after the receipt of the user input. The contextualinformation can include user-specific data, vocabulary, and/orpreferences relevant to the user input. In some examples, the contextualinformation also includes software and hardware states of the userdevice at the time the user request is received, and/or informationrelated to the surrounding environment of the user at the time that theuser request was received. In some examples, I/O processing module 728can also send follow-up questions to, and receive answers from, the userregarding the user request. When a user request is received by I/Oprocessing module 728 and the user request can include speech input, I/Oprocessing module 728 can forward the speech input to STT processingmodule 730 (or a speech recognizer) for speech-to-text conversions.

STT processing module 730 can include one or more ASR systems. The oneor more ASR systems can process the speech input that is receivedthrough I/O processing module 728 to produce a recognition result. EachASR system can include a front-end speech pre-processor. The front-endspeech pre-processor can extract representative features from the speechinput. For example, the front-end speech pre-processor can perform aFourier transform on the speech input to extract spectral features thatcharacterize the speech input as a sequence of representativemulti-dimensional vectors. Further, each ASR system can include one ormore speech recognition models (e.g., acoustic models and/or languagemodels) and can implement one or more speech recognition engines.Examples of speech recognition models can include Hidden Markov Models,Gaussian-Mixture Models, Deep Neural Network Models, n-gram languagemodels, and other statistical models. Examples of speech recognitionengines can include the dynamic time warping based engines and weightedfinite-state transducers (WFST) based engines. The one or more speechrecognition models and the one or more speech recognition engines can beused to process the extracted representative features of the front-endspeech pre-processor to produce intermediate recognitions results (e.g.,phonemes, phonemic strings, and sub-words), and ultimately, textrecognition results (e.g., words, word strings, or sequence of tokens).In some examples, the speech input can be processed at least partiallyby a third-party service or on the user's device (e.g., device 104, 200,400, or 600) to produce the recognition result. Once STT processingmodule 730 produces recognition results containing a text string (e.g.,words, or sequence of words, or sequence of tokens), the recognitionresult can be passed to natural language processing module 732 forintent deduction.

More details on the speech-to-text processing are described in U.S.Utility application Ser. No. 13/236,942 for “Consolidating SpeechRecognition Results,” filed on Sep. 20, 2011, the entire disclosure ofwhich is incorporated herein by reference.

In some examples, STT processing module 730 can include and/or access avocabulary of recognizable words via phonetic alphabet conversion module731. Each vocabulary word can be associated with one or more candidatepronunciations of the word represented in a speech recognition phoneticalphabet. In particular, the vocabulary of recognizable words caninclude a word that is associated with a plurality of candidatepronunciations. For example, the vocabulary may include the word“tomato” that is associated with the candidate pronunciations of /

/ and /

/. Further, vocabulary words can be associated with custom candidatepronunciations that are based on previous speech inputs from the user.Such custom candidate pronunciations can be stored in STT processingmodule 730 and can be associated with a particular user via the user'sprofile on the device. In some examples, the candidate pronunciationsfor words can be determined based on the spelling of the word and one ormore linguistic and/or phonetic rules. In some examples, the candidatepronunciations can be manually generated, e.g., based on known canonicalpronunciations.

In some examples, the candidate pronunciations can be ranked based onthe commonness of the candidate pronunciation. For example, thecandidate pronunciation /

/ can be ranked higher than /

/, because the former is a more commonly used pronunciation (e.g., amongall users, for users in a particular geographical region, or for anyother appropriate subset of users). In some examples, candidatepronunciations can be ranked based on whether the candidatepronunciation is a custom candidate pronunciation associated with theuser. For example, custom candidate pronunciations can be ranked higherthan canonical candidate pronunciations. This can be useful forrecognizing proper nouns having a unique pronunciation that deviatesfrom canonical pronunciation. In some examples, candidate pronunciationscan be associated with one or more speech characteristics, such asgeographic origin, nationality, or ethnicity. For example, the candidatepronunciation /

/ can be associated with the United States, whereas the candidatepronunciation /

/ can be associated with Great Britain. Further, the rank of thecandidate pronunciation can be based on one or more characteristics(e.g., geographic origin, nationality, ethnicity, etc.) of the userstored in the user's profile on the device. For example, it can bedetermined from the user's profile that the user is associated with theUnited States. Based on the user being associated with the UnitedStates, the candidate pronunciation /

/ (associated with the United States) can be ranked higher than thecandidate pronunciation /

/ (associated with Great Britain). In some examples, one of the rankedcandidate pronunciations can be selected as a predicted pronunciation(e.g., the most likely pronunciation).

When a speech input is received, STT processing module 730 can be usedto determine the phonemes corresponding to the speech input (e.g., usingan acoustic model), and then attempt to determine words that match thephonemes (e.g., using a language model). For example, if STT processingmodule 730 can first identify the sequence of phonemes /

/ corresponding to a portion of the speech input, it can then determine,based on vocabulary index 744, that this sequence corresponds to theword “tomato.”

In some examples, STT processing module 730 can use approximate matchingtechniques to determine words in a voice input. Thus, for example, theSTT processing module 730 can determine that the sequence of phonemes /

/ corresponds to the word “tomato,” even if that particular sequence ofphonemes is not one of the candidate sequence of phonemes for that word.

Natural language processing module 732 (“natural language processor”) ofthe digital assistant can take the sequence of words or tokens (“tokensequence”) generated by STT processing module 730, and attempt toassociate the token sequence with one or more “actionable intents”recognized by the digital assistant. An “actionable intent” canrepresent a task that can be performed by the digital assistant, and canhave an associated task flow implemented in task flow models 754. Theassociated task flow can be a series of programmed actions and stepsthat the digital assistant takes in order to perform the task. The scopeof a digital assistant's capabilities can be dependent on the number andvariety of task flows that have been implemented and stored in task flowmodels 754, or in other words, on the number and variety of “actionableintents” that the digital assistant recognizes. The effectiveness of thedigital assistant, however, can also be dependent on the assistant'sability to infer the correct “actionable intent(s)” from the userrequest expressed in natural language.

In some examples, in addition to the sequence of words or tokensobtained from STT processing module 730, natural language processingmodule 732 can also receive contextual information associated with theuser request, e.g., from I/O processing module 728. The natural languageprocessing module 732 can optionally use the contextual information toclarify, supplement, and/or further define the information contained inthe token sequence received from STT processing module 730. Thecontextual information can include, for example, user preferences,hardware, and/or software states of the user device, sensor informationcollected before, during, or shortly after the user request, priorinteractions (e.g., dialogue) between the digital assistant and theuser, and the like. As described herein, contextual information can bedynamic, and can change with time, location, content of the dialogue,and other factors.

In some examples, the natural language processing can be based on, e.g.,ontology 760. Ontology 760 can be a hierarchical structure containingmany nodes, each node representing either an “actionable intent” or a“property” relevant to one or more of the “actionable intents” or other“properties.” As noted above, an “actionable intent” can represent atask that the digital assistant is capable of performing, i.e., it is“actionable” or can be acted on. A “property” can represent a parameterassociated with an actionable intent or a sub-aspect of anotherproperty. A linkage between an actionable intent node and a propertynode in ontology 760 can define how a parameter represented by theproperty node pertains to the task represented by the actionable intentnode.

In some examples, ontology 760 can be made up of actionable intent nodesand property nodes. Within ontology 760, each actionable intent node canbe linked to one or more property nodes either directly or through oneor more intermediate property nodes. Similarly, each property node canbe linked to one or more actionable intent nodes either directly orthrough one or more intermediate property nodes. For example, as shownin FIG. 7C, ontology 760 can include a “restaurant reservation” node(i.e., an actionable intent node). Property nodes “restaurant,”“date/time” (for the reservation), and “party size” can each be directlylinked to the actionable intent node (i.e., the “restaurant reservation”node).

In addition, property nodes “cuisine,” “price range,” “phone number,”and “location” can be sub-nodes of the property node “restaurant,” andcan each be linked to the “restaurant reservation” node (i.e., theactionable intent node) through the intermediate property node“restaurant.” For another example, as shown in FIG. 7C, ontology 760 canalso include a “set reminder” node (i.e., another actionable intentnode). Property nodes “date/time” (for setting the reminder) and“subject” (for the reminder) can each be linked to the “set reminder”node. Since the property “date/time” can be relevant to both the task ofmaking a restaurant reservation and the task of setting a reminder, theproperty node “date/time” can be linked to both the “restaurantreservation” node and the “set reminder” node in ontology 760.

An actionable intent node, along with its linked concept nodes, can bedescribed as a “domain.” In the present discussion, each domain can beassociated with a respective actionable intent, and refers to the groupof nodes (and the relationships there between) associated with theparticular actionable intent. For example, ontology 760 shown in FIG. 7Ccan include an example of restaurant reservation domain 762 and anexample of reminder domain 764 within ontology 760. The restaurantreservation domain includes the actionable intent node “restaurantreservation,” property nodes “restaurant,” “date/time,” and “partysize,” and sub-property nodes “cuisine,” “price range,” “phone number,”and “location.” Reminder domain 764 can include the actionable intentnode “set reminder,” and property nodes “subject” and “date/time.” Insome examples, ontology 760 can be made up of many domains. Each domaincan share one or more property nodes with one or more other domains. Forexample, the “date/time” property node can be associated with manydifferent domains (e.g., a scheduling domain, a travel reservationdomain, a movie ticket domain, etc.), in addition to restaurantreservation domain 762 and reminder domain 764.

While FIG. 7C illustrates two example domains within ontology 760, otherdomains can include, for example, “find a movie,” “initiate a phonecall,” “find directions,” “schedule a meeting,” “send a message,” and“provide an answer to a question,” “read a list,” “providing navigationinstructions,” “provide instructions for a task” and so on. A “send amessage” domain can be associated with a “send a message” actionableintent node, and may further include property nodes such as“recipient(s),” “message type,” and “message body.” The property node“recipient” can be further defined, for example, by the sub-propertynodes such as “recipient name” and “message address.”

In some examples, ontology 760 can include all the domains (and henceactionable intents) that the digital assistant is capable ofunderstanding and acting upon. In some examples, ontology 760 can bemodified, such as by adding or removing entire domains or nodes, or bymodifying relationships between the nodes within the ontology 760.

In some examples, nodes associated with multiple related actionableintents can be clustered under a “super domain” in ontology 760. Forexample, a “travel” super-domain can include a cluster of property nodesand actionable intent nodes related to travel. The actionable intentnodes related to travel can include “airline reservation,” “hotelreservation,” “car rental,” “get directions,” “find points of interest,”and so on. The actionable intent nodes under the same super domain(e.g., the “travel” super domain) can have many property nodes incommon. For example, the actionable intent nodes for “airlinereservation,” “hotel reservation,” “car rental,” “get directions,” and“find points of interest” can share one or more of the property nodes“start location,” “destination,” “departure date/time,” “arrivaldate/time,” and “party size.”

In some examples, each node in ontology 760 can be associated with a setof words and/or phrases that are relevant to the property or actionableintent represented by the node. The respective set of words and/orphrases associated with each node can be the so-called “vocabulary”associated with the node. The respective set of words and/or phrasesassociated with each node can be stored in vocabulary index 744 inassociation with the property or actionable intent represented by thenode. For example, returning to FIG. 7B, the vocabulary associated withthe node for the property of “restaurant” can include words such as“food,” “drinks,” “cuisine,” “hungry,” “eat,” “pizza,” “fast food,”“meal,” and so on. For another example, the vocabulary associated withthe node for the actionable intent of “initiate a phone call” caninclude words and phrases such as “call,” “phone,” “dial,” “ring,” “callthis number,” “make a call to,” and so on. The vocabulary index 744 canoptionally include words and phrases in different languages.

Natural language processing module 732 can receive the token sequence(e.g., a text string) from STT processing module 730, and determine whatnodes are implicated by the words in the token sequence. In someexamples, if a word or phrase in the token sequence is found to beassociated with one or more nodes in ontology 760 (via vocabulary index744), the word or phrase can “trigger” or “activate” those nodes. Basedon the quantity and/or relative importance of the activated nodes,natural language processing module 732 can select one of the actionableintents as the task that the user intended the digital assistant toperform. In some examples, the domain that has the most “triggered”nodes can be selected. In some examples, the domain having the highestconfidence value (e.g., based on the relative importance of its varioustriggered nodes) can be selected. In some examples, the domain can beselected based on a combination of the number and the importance of thetriggered nodes. In some examples, additional factors are considered inselecting the node as well, such as whether the digital assistant haspreviously correctly interpreted a similar request from a user.

User data 748 can include user-specific information, such asuser-specific vocabulary, user preferences, user address, user's defaultand secondary languages, user's contact list, and other short-term orlong-term information for each user. In some examples, natural languageprocessing module 732 can use the user-specific information tosupplement the information contained in the user input to further definethe user intent. For example, for a user request “invite my friends tomy birthday party,” natural language processing module 732 can be ableto access user data 748 to determine who the “friends” are and when andwhere the “birthday party” would be held, rather than requiring the userto provide such information explicitly in his/her request.

Other details of searching an ontology based on a token string isdescribed in U.S. Utility application Ser. No. 12/341,743 for “Methodand Apparatus for Searching Using An Active Ontology,” filed Dec. 22,2008, the entire disclosure of which is incorporated herein byreference.

In some examples, once natural language processing module 732 identifiesan actionable intent (or domain) based on the user request, naturallanguage processing module 732 can generate a structured query torepresent the identified actionable intent. In some examples, thestructured query can include parameters for one or more nodes within thedomain for the actionable intent, and at least some of the parametersare populated with the specific information and requirements specifiedin the user request. For example, the user may say “Make me a dinnerreservation at a sushi place at 7.” In this case, natural languageprocessing module 732 can be able to correctly identify the actionableintent to be “restaurant reservation” based on the user input. Accordingto the ontology, a structured query for a “restaurant reservation”domain may include parameters such as {Cuisine}, {Time}, {Date}, {PartySize}, and the like. In some examples, based on the speech input and thetext derived from the speech input using STT processing module 730,natural language processing module 732 can generate a partial structuredquery for the restaurant reservation domain, where the partialstructured query includes the parameters {Cuisine=“Sushi”} and {Time=“7pm”}. However, in this example, the user's speech input containsinsufficient information to complete the structured query associatedwith the domain. Therefore, other necessary parameters such as {PartySize} and {Date} may not be specified in the structured query based onthe information currently available. In some examples, natural languageprocessing module 732 can populate some parameters of the structuredquery with received contextual information. For example, in someexamples, if the user requested a sushi restaurant “near me,” naturallanguage processing module 732 can populate a {location} parameter inthe structured query with GPS coordinates from the user device.

In some examples, natural language processing module 732 can pass thegenerated structured query (including any completed parameters) to taskflow processing module 736 (“task flow processor”). Task flow processingmodule 736 can be configured to receive the structured query fromnatural language processing module 732, complete the structured query,if necessary, and perform the actions required to “complete” the user'sultimate request. In some examples, the various procedures necessary tocomplete these tasks can be provided in task flow models 754. In someexamples, task flow models 754 can include procedures for obtainingadditional information from the user and task flows for performingactions associated with the actionable intent.

As described above, in order to complete a structured query, task flowprocessing module 736 may need to initiate additional dialogue with theuser in order to obtain additional information, and/or disambiguatepotentially ambiguous speech inputs. When such interactions arenecessary, task flow processing module 736 can invoke dialogue flowprocessing module 734 to engage in a dialogue with the user. In someexamples, dialogue flow processing module 734 can determine how (and/orwhen) to ask the user for the additional information and receives andprocesses the user responses. The questions can be provided to andanswers can be received from the users through I/O processing module728. In some examples, dialogue flow processing module 734 can presentdialogue output to the user via audio and/or visual output, and receivesinput from the user via spoken or physical (e.g., clicking) responses.Continuing with the example above, when task flow processing module 736invokes dialogue flow processing module 734 to determine the “partysize” and “date” information for the structured query associated withthe domain “restaurant reservation,” dialogue flow processing module 734can generate questions such as “For how many people?” and “On whichday?” to pass to the user. Once answers are received from the user,dialogue flow processing module 734 can then populate the structuredquery with the missing information, or pass the information to task flowprocessing module 736 to complete the missing information from thestructured query.

Once task flow processing module 736 has completed the structured queryfor an actionable intent, task flow processing module 736 can proceed toperform the ultimate task associated with the actionable intent.Accordingly, task flow processing module 736 can execute the steps andinstructions in the task flow model according to the specific parameterscontained in the structured query. For example, the task flow model forthe actionable intent of “restaurant reservation” can include steps andinstructions for contacting a restaurant and actually requesting areservation for a particular party size at a particular time. Forexample, using a structured query such as: {restaurant reservation,restaurant=ABC Café, date=3/12/2012, time=7 pm, party size=5}, task flowprocessing module 736 can perform the steps of: (1) logging onto aserver of the ABC Café or a restaurant reservation system such asOPENTABLE®, (2) entering the date, time, and party size information in aform on the website, (3) submitting the form, and (4) making a calendarentry for the reservation in the user's calendar.

In some examples, task flow processing module 736 can employ theassistance of service processing module 738 (“service processingmodule”) to complete a task requested in the user input or to provide aninformational answer requested in the user input. For example, serviceprocessing module 738 can act on behalf of task flow processing module736 to make a phone call, set a calendar entry, invoke a map search,invoke or interact with other user applications installed on the userdevice, and invoke or interact with third-party services (e.g., arestaurant reservation portal, a social networking website, a bankingportal, etc.). In some examples, the protocols and applicationprogramming interfaces (API) required by each service can be specifiedby a respective service model among service models 756. Serviceprocessing module 738 can access the appropriate service model for aservice and generate requests for the service in accordance with theprotocols and APIs required by the service according to the servicemodel.

For example, if a restaurant has enabled an online reservation service,the restaurant can submit a service model specifying the necessaryparameters for making a reservation and the APIs for communicating thevalues of the necessary parameter to the online reservation service.When requested by task flow processing module 736, service processingmodule 738 can establish a network connection with the onlinereservation service using the web address stored in the service model,and send the necessary parameters of the reservation (e.g., time, date,party size) to the online reservation interface in a format according tothe API of the online reservation service.

In some examples, natural language processing module 732, dialogue flowprocessing module 734, and task flow processing module 736 can be usedcollectively and iteratively to infer and define the user's intent,obtain information to further clarify and refine the user intent, andfinally generate a response (i.e., an output to the user, or thecompletion of a task) to fulfill the user's intent. The generatedresponse can be a dialogue response to the speech input that at leastpartially fulfills the user's intent. Further, in some examples, thegenerated response can be output as a speech output. In these examples,the generated response can be sent to speech synthesis module 740 (e.g.,speech synthesizer) where it can be processed to synthesize the dialogueresponse in speech form. In yet other examples, the generated responsecan be data content relevant to satisfying a user request in the speechinput.

Speech synthesis module 740 can be configured to synthesize speechoutputs for presentation to the user. Speech synthesis module 740synthesizes speech outputs based on text provided by the digitalassistant. For example, the generated dialogue response can be in theform of a text string. Speech synthesis module 740 can convert the textstring to an audible speech output. Speech synthesis module 740 can useany appropriate speech synthesis technique in order to generate speechoutputs from text, including, but not limited, to concatenativesynthesis, unit selection synthesis, diphone synthesis, domain-specificsynthesis, formant synthesis, articulatory synthesis, hidden Markovmodel (HMM) based synthesis, and sinewave synthesis. In some examples,speech synthesis module 740 can be configured to synthesize individualwords based on phonemic strings corresponding to the words. For example,a phonemic string can be associated with a word in the generateddialogue response. The phonemic string can be stored in metadataassociated with the word. Speech synthesis model 740 can be configuredto directly process the phonemic string in the metadata to synthesizethe word in speech form.

In some examples, instead of (or in addition to) using speech synthesismodule 740, speech synthesis can be performed on a remote device (e.g.,the server system 108), and the synthesized speech can be sent to theuser device for output to the user. For example, this can occur in someimplementations where outputs for a digital assistant are generated at aserver system. And because server systems generally have more processingpower or resources than a user device, it can be possible to obtainhigher quality speech outputs than would be practical with client-sidesynthesis.

Additional details on digital assistants can be found in the U.S.Utility application Ser. No. 12/987,982, entitled “Intelligent AutomatedAssistant,” filed Jan. 10, 2011, and U.S. Utility application Ser. No.13/251,088, entitled “Generating and Processing Task Items ThatRepresent Tasks to Perform,” filed Sep. 30, 2011, the entire disclosuresof which are incorporated herein by reference.

4. Exemplary Functions of a Digital Assistant

FIGS. 8A-8I, 9A-9B, and 10A-10E illustrate functionality of providingspoken status information by a device 800. In some examples, device 800can implement a digital assistant system (e.g., digital assistant system700) according to various examples. In some examples, device 800, aserver (e.g., server 108), or a combination thereof, may implement adigital assistant system (e.g., digital assistant system 700). Withreferences to FIGS. 8A-8I, 9A-9B, and 10A-10E, in some examples, thedigital assistant of device 800 can receive one or more speech inputs,such as 824A-I, 924A-B, 1024A-D, and 1036 from a user 810. User 810 mayprovide various speech inputs for the purpose of, for example, obtainingspoken status information associated with one or more electronicdevices. The one or more electronic devices can include device 800(e.g., a smartphone), a watch 830, a headset 840, a tablet 850, aheadset case (not shown), a TV set-top box (not shown), a laptopcomputer, a desktop computer, or the like. Device 800 can be implementedusing, for example, device 104, 200, or 400.

In some embodiments, the status information of one or more of theelectronic devices can include at least one of battery statusinformation, connectivity status information, operating mode statusinformation, location status information, device configuration statusinformation, or the like. The battery status information may indicatethe battery level of an electronic device. For example, the batterystatus information may indicate the percentage of the battery remainingof a battery powered device (e.g., a headset, a smartphone, a tablet,etc.), one or more auxiliary battery packs, one or more cradles forpowering devices, or the like. The connectivity status information mayindicate wired or wireless connectivity of an electronic device. In someexamples, the connectivity status information can indicate the Wi-Ficonnectivity, the Bluetooth connectivity, the cellular connectivity, thepersonal hotspot connectivity, etc. of the electronic device. Theconnectivity status information may indicate, for example, that theWi-Fi connectivity is not currently enabled on device 800. The operatingmode status information may indicate the electronic device's currentoperating mode. For example, the operating mode status information mayindicate that the electronic device is currently operating in a normalmode with all or commonly used functionalities enabled, in an airplanemode with all Wi-Fi connectivity and cellular connectivity disabled, orin a do-not-disturb mode with incoming call/message alert capabilitiesdisabled. The location status information may indicate the currentlocation (e.g., GPS coordinates) of the electronic device. The deviceconfiguration status information may indicate the current configurationstatus such as the Bluetooth pairing status, the screen brightnessconfiguration status, the sound level configuration status, or the like.While the systems and processes described below use the battery statusinformation as examples, it is appreciated that the described systemsand processes can be used or adapted to provide other types of statusinformation to the user.

With reference to FIGS. 8A-8I, 9A-9B, and 10A-10E, device 800 canreceive speech inputs directly from user 810 or indirectly throughanother electronic device that is communicatively connected to device800. Device 800 (e.g., a smartphone) can receive speech inputs directlyfrom user 810 via, for example, a microphone of device 800. Device 800can also receive speech inputs indirectly through, for example, headset840, watch 830, tablet 850, or the like. For instance, user 810 may wearheadset 840 around the user's ears and speak to headset 840. Headset 840receives the speech input from user 810 and transmits the speech inputor a representation of it to device 800 via, for example, a Bluetoothconnection between headset 840 and device 800. Similarly, user 810 mayspeak to watch 830, which can transmit the speech input or arepresentation of it to device 800.

With reference to FIGS. 8A-8I, 9A-9B, and 10A-10E, any one of the one ormore electronic devices (e.g., device 800, watch 830, headset 840,tablet 850, etc.) may be an invoking device. An invoking device receivesthe speech input directly from user 810. For example, if headset 840receives the speech input directly from user 810, headset 840 can be theinvoking device. In some examples, the invoking device can be device 800or an electronic device communicatively connected to device 800, such aswatch 830 and tablet 850.

With reference to FIGS. 8A-8I, 9A-9B, and 10A-10E, in response toreceiving a speech input, either directly from user 810 or indirectlythrough another electronic device, device 800 can determine a userintent based on the speech input. As described above, in some examples,device 800 can receive a speech input via an I/O processing module(e.g., I/O processing module 728 as shown in FIG. 7B), an STT processingmodule (e.g., STT processing module 730 as shown in FIG. 7B), and anatural language processing module (e.g., natural language processingmodule 732 as shown in FIG. 7B). As described, the I/O processing modulecan forward the speech input to an STT processing module (or a speechrecognizer) for speech-to-text conversions. The speech-to-textconversion can generate text based on the speech input. As describedabove, the STT processing module can generate a sequence of words ortokens (“token sequence”) and provide the token sequence to the naturallanguage processing module. The natural language processing moduleperforms natural language processing of the text, and determines theuser intent based on a result of the natural language processing. Forexample, the natural language processing module may attempt to associatethe token sequence with one or more actionable intents recognized by thedigital assistant. Various examples of determination of the user intentare provided below in more detail with respect to FIGS. 8A-8I, 9A-9B,and 10A-10E.

With reference to FIG. 8A, in some examples, to determine the userintent, device 800 can determine whether a speech input includes one ormore references identifying at least one of the one or more electronicdevices. A reference can include one or more words or a phrasespecifically identifying an electronic device. For example, user 810 maywish to obtain the status information of his watch and thus providespeech input 824A. Speech input 824A can include, for example, “How muchbattery do I have left on my watch?” In speech input 824A, the phrase“my watch” is a reference. Similarly, a reference can include “mytablet,” “my smartphone,” “my wife's tablet,” or the like.

In some examples, in accordance with a determination that speech input824A includes one or more references (e.g., “my watch”), device 800 candetermine the user intent based on one or more references. For example,based on the reference “my watch” included in speech input 824A, device800 can determine that the user intent is to obtain status informationof his or her watch, not other electronic devices.

As shown in FIG. 8A, in some embodiments, after the determination of theuser intent, device 800 can request, in accordance with the user intent,status information associated with one or more of the electronicdevices. As described, device 800 can include a task flow processingmodule (e.g., task flow processing module 736 as shown in FIG. 7B), aservice processing module (e.g., service processing module 738 as shownin FIG. 7B), and a dialog processing module (e.g., dialog processingmodule 734 as shown in FIG. 7B). One or more of these modules of device800 can facilitate requesting of the status information. For example, asshown in FIG. 8A, based on speech input 824A, device 800 may determinethat the user intent to is to obtain status information of his or herwatch. In accordance with the user intent, device 800 can identify atleast one of one or more electronic devices to obtain the statusinformation. In some examples, device 800 can identify whether at leastone of the electronic devices communicatively connected to device 800corresponds to the device for which the status information is to berequested, as indicated in the user intent. For example, if the userintent is to obtain the battery status information of his or her watch,device 800 can detect that watch 830 is communicatively connected (e.g.,via a Bluetooth connection) to device 800 and is the electronic devicefor which the status information is to be requested.

In some examples, after identifying one or more electronic devices forwhich the status information is to be requested, device 800 cancommunicate a request for the status information to the identifieddevice for which the status information is to be requested. For example,after the identification of watch 830, device 800 can transmit a requestto watch 830 via a wired or wireless connection (e.g., a Bluetoothconnection) to obtain the status information. After receiving therequest, watch 830 obtains the requested status information (e.g., thecurrent remaining battery percentage), and transmits it back to device800.

As shown in FIG. 8A, device 800 receives the status information fromwatch 830, and generates a spoken output representing the statusinformation. As described, device 800 can include a speech synthesismodule (e.g., speech synthesis module 740 as shown in FIG. 7B). Thespeech synthesis module can process to synthesize the received statusinformation in speech form. For example, in FIG. 8A, device 800 cansynthesize the status information provided by watch 830 to generate aspoken output. The spoken output may include an audio representation ofthe requested status information of watch 830 such as “It's at 88%,”indicating that the remaining battery of watch 830 is currently at 88%.In some embodiments, the spoken output is provided to the user by device800.

With reference to FIG. 8B, in some examples, a speech input may includereferences identifying a plurality of electronic devices. For example,user 810 may wish to obtain the status information of his watch and hisheadset. User 810 may thus provide speech input 824B including, forexample, “How are the battery levels on my watch and my headset?” Thephrases “my watch” and “my headset” are references.

In some examples, in accordance with a determination that speech input824B includes a plurality of references (e.g., “my watch” and “myheadset”), device 800 can determine the user intent based on pluralityof references. For example, based on the references “my watch” and “myheadset” included in speech input 824B, device 800 can determine thatthe user intent is to obtain status information of his or her watch andheadset, not other electronic devices.

As shown in FIG. 8B, in some embodiments, after determining the userintent, device 800 can request, in accordance with the user intent,status information associated with one or more of the electronicdevices. In some examples, in accordance with the user intent, device800 can identify whether the electronic devices communicativelyconnected to device 800 correspond to the devices for which the statusinformation is to be requested. For example, device 800 can detect thatwatch 830, headset 840, and tablet 850 are all communicatively connected(e.g., via Bluetooth connections) to device 800. Device 800 can furtheridentify that watch 830 and headset 840 correspond to the devices forwhich the status information is to be requested, but not tablet 850.

In some examples, after identifying the plurality of electronic devicesfor which the status information is to be requested, device 800 cancommunicate a request for the status information to the each of theidentified devices (e.g., watch 830 and headset 840) for which thestatus information is to be requested. After receiving the request,watch 830 and headset 840 obtain the requested status information (e.g.,the current remaining battery percentage), and transmit it back todevice 800. In some examples, headset 840 can include a left earbud anda right earbud. Headset 840 may also be associated with a case forcharging the earbuds. As a result, the status information of headset 840can include the overall status of headset 840, the status of the leftearbud, the status of the right earbud, the status of the case, or acombination thereof.

As shown in FIG. 8B, device 800 can receive the status information fromwatch 830 and headset 840. For example, device 800 may receive theoverall battery status of headset 840; the battery statuses of the leftearbud and the right earbud; the battery status of the case associatedwith headset 840; or a combination thereof. Based on the received statusinformation, device 800 can generate a spoken output representing thestatus information. For example, in FIG. 8B, device 800 can synthesizethe status information provided by watch 830 and headset 840 to generatea spoken output 828B include an audio representation of the statusinformation such as “Your watch is at 88%, your headset is at 45%,”indicating that the remaining battery of watch 830 is at 88% and theremaining battery of headset 840 is at 45%.

As shown in FIG. 8B, in some embodiments, device 800 can generate thespoken output in an order that corresponds to the order of thereferences included in the speech input. For example, in speech input824B, the order of the references is such that the reference “my watch”is followed by the reference “my headset.” Correspondingly, spokenoutput 828B can be generated in the order such that the statusinformation of watch 830 is followed by the status information ofheadset 840. For example, spoken output 828B includes an audiorepresentation of the status information such as “Your watch is at 88%,your headset is at 45%.”

As described, in some examples, to determine the user intent, device 800can determine whether a speech input includes one or more referencesidentifying at least one of the one or more electronic devices. Withreference to FIGS. 8C and 8D, in some examples, device 800 may determinethat the speech input does not include any references. Instead, thespeech input may include information that does not specifically identifyone or more electronic devices for which the status information is to berequested. For example, as shown in FIG. 8C, user 810 may provide aspeech input 824C including, for example, “How is the battery level?” Asshown in FIG. 8D, user 810 may provide a speech input 824D, including,for example, “What are my battery levels?” Accordingly, speech inputs824C and 824D include information without a reference identifying atleast one electronic device for which the status information is to berequested.

With reference to FIGS. 8C and 8D, in some embodiments, in accordancewith a determination that a speech input includes information without areference identifying at least one electronic device for which thestatus information is to be requested, device 800 can determine the userintent based on an expression of the speech input. In some examples, todetermine the user intent, device 800 can determine whether a speechinput includes a singular form expression or a plural form expression.For example, in FIG. 8C, speech input 824C includes “How is the batterylevel?” Accordingly, device 800 can determine that speech input 824Cincludes a singular form expression, based on the indication of thesingular verb “is” and the singular noun “level.” As another example, inFIG. 8D, speech input 824D includes “What are my battery levels?”Accordingly, device 800 can determine that speech input 824D includes aplural form expression, based on the indication of the plural verb “are”and the plural noun “levels”.

With reference to FIG. 8C, in some embodiments, in accordance with adetermination that the speech input includes a singular form expression,device 800 can determine, from one or more electronic devices, a singleelectronic device for which the status information is to be requested.In some examples, device 800 can determine the single electronic devicebased on context information such as a pre-determined configuration, auser preference, user-specific data, or the like. For example, thecontext information may indicate that the single electronic device forwhich the status information is to be requested is the invoking deviceif the speech input includes a singular form expression. As described,the invoking device receives the speech input directly from user 810.The invoking device can be device 800 itself (e.g., a smartphone) or anelectronic device communicatively connected to device 800 (e.g., headset840). For example, if the invoking device is device 800 itself, device800 can determine that the single electronic device for which the statusinformation is to be requested is itself. As another example, a user mayfrequently check the status of watch 830 and thus the contextinformation may indicate that the single electronic device for which thestatus information is to be requested is watch 830 if the speech inputincludes a singular form expression. According to the contextinformation, device 800 can determine the single electronic device forwhich the status information is to be requested is watch 830.

Similar to those described above, in some embodiments, after determiningthe single electronic device for which the status information is to berequested, device 800 can request the status information (e.g., thebattery status information) associated with the single electronicdevice, receive the status information, and generate a spoken outputrepresenting the status information. In some examples, device 800 canprovide the spoken output to user 810. For example, device 800 canprovide spoken output 828C including an audio representation of thestatus information such as “Your phone is at 88%.”

With reference to FIG. 8D, in some embodiments, in accordance with adetermination that the speech input includes a plural form expression,device 800 can determine a plurality of electronic devices for whichstatus information is to be requested. For example, device 800 candetermine the plurality of electronic devices based on contextinformation such as a pre-determined configuration, a user preference,user-specific data, or the like. For example, the context informationmay indicate that the plurality of electronic devices for which thestatus information is to be requested include the invoking device. Asdescribed, the invoking device can be, for example, device 800 itself(e.g., a smartphone) or an electronic device communicatively connectedto device 800 (e.g., headset 840). In some examples, the contextinformation may also indicate that the plurality of electronic devicesfor which the status information is to be requested include oneelectronic device communicatively connected to the invoking device. Forexample, the context information may indicate that the plurality ofelectronic devices for which the status information is to be requestedinclude the invoking device and one other electronic device that user810 is or is not currently operating. In some examples, the contextinformation may indicate that the plurality of electronic devices forwhich the status information is to be requested include all electronicdevices communicatively connected to device 800. Thus, for example, asshown in FIG. 8D, if speech input 824D includes a plural formexpression, device 800 can determine that the status information of allelectronic devices (e.g., watch 830, headset 840, and tablet 850) anditself is to be requested.

Similar to those described above, in some embodiments, after thedetermination of the plurality of electronic devices for which thestatus information is to be requested, device 800 can request the statusinformation (e.g., the battery status information) associated with theplurality of electronic devices, receive the status information, andgenerate a spoken output representing the status information. In someexamples, device 800 can provide the spoken output to user 810. Forexample, device 800 can provide spoken output 828D including an audiorepresentation of the status information such as “Your phone is at 35,headset at 92, watch at 88, and tablet at 92.”

As described, in some examples, to determine the user intent, device 800can determine whether a speech input includes one or more referencesidentifying at least one of the one or more electronic devices. Withreference to FIGS. 8E and 8F, device 800 can determine that the speechinput does not include one or more references. Instead, the speech inputmay include information that does not specifically identify one or moreelectronic devices for which the status information is to be requested.For example, as shown in FIG. 8E, user 810 may provide a speech input824E such as “What is the battery level on this?” As shown in FIG. 8F,user 810 may provide a speech input 824F such as “Is everythingcharged?” Accordingly, speech inputs 824E and 824F include informationwithout a reference identifying at least one of the one or moreelectronic devices.

With reference to FIGS. 8E and 8F, in some embodiments, in accordancewith a determination that the speech input includes information thatdoes not identify at least one electronic device for which the statusinformation is to be requested, device 800 can determine the user intentbased on one or more keywords included in the speech input. In someexamples, a keyword may be used to infer the user intent. A keyword maynot include a reference identifying a specific electronic device. Akeyword can include, for example, the words “this,” “that,” “all,”“everything,” “anything,” or the like. As an example, as shown in FIG.8E, speech input 824E includes a keyword “this” within the expression“What is the battery level on this?” As another example, as shown inFIG. 8F, speech input 824F includes a keyword “everything” within theexpression “Is everything charged?” As another example, a speech inputmay also include expressions such as “What are all my battery levels?”or “Is anything low on battery?”

In some embodiments, with reference to FIGS. 8E and 8F, device 800 candetermine whether the speech input includes one or more keywords. Forexample, device 800 can determine that both speech inputs 824E and 824Finclude at least one keyword (e.g., the words “this” or “everything”).In accordance with a determination that the speech input includes one ormore keywords, device 800 can determine, from the one or more electronicdevices, at least one electronic device for which the status informationis to be requested. In some examples, device 800 can determine the atleast one electronic device based on context information such as apre-determined configuration, a user preference, user-specific data, orthe like. For example, based on context information, device 800 maydetermine that the keyword “this” corresponds to the invoking device(e.g., the electronic device that receives speech input 824E) or anelectronic device that user 810 is currently operating. As shown in FIG.8E, device 800 may determine that the keyword “this” in speech input824E corresponds to device 800 itself, which may be the invoking device.

As another example, based on the context information, device 800 maydetermine that the keyword “everything” corresponds to all electronicdevices. As shown in FIG. 8F, device 800 may determine that the keyword“everything” in speech input 824F corresponds to all electronic devicescommunicatively connected to device 800 (e.g., watch 830, headset 840,and tablet 850) as well as device 800 itself.

In some embodiments, based on the one or more keywords, device 800 candetermine at least one electronic device for which status information isto be requested. For example, as shown in FIG. 8E, based on thedetermination that the keyword “this” corresponds the invoking device(e.g., device 800 itself), device 800 can determine that the statusinformation of itself is to be requested. As another example, as shownin FIG. 8F, based on the determination that the keyword “everything”corresponds to all electronic devices (e.g., device 800 itself, watch830, headset 840, and tablet 850), device 800 can determine that thestatus information of all electronic devices is to be requested.

Similar to those described above, in some embodiments, after thedetermination of the at least one electronic device for which the statusinformation is to be requested, device 800 can request the statusinformation (e.g., the battery status information) associated with theat least one electronic device, receive the status information, andgenerate a spoken output representing the status information. Forexample, in FIG. 8E, device 800 can generate spoken output 828Eincluding an audio representation of the status information such as“Your phone is at 88%.” As another example, in FIG. 8F, device 800 cangenerate spoken output 828F including an audio representation of thestatus information such as “Your tablet and phone could use a charge,they're both below 30%. Your watch and headset are both above 80%.”

In some embodiments, device 800 can generate a spoken output using oneor more paraphrased responses. As shown in FIG. 8F, instead providing aspoken output including an audio representation of the statusinformation of each device one-by-one, device 800 can generate thespoken output using a paraphrased response. For example, instead ofproviding “You tablet is at 30%, your phone is at 30%, your watch is at55%, and your headset is at 88%;” device 800 can provide a paraphraseresponse such as “Your tablet and phone could use a charge, they're bothbelow 30%. Your watch and headset are both above 80%.” A spoken outputusing a paraphrased response can provide the same or similar statusinformation in a different form. As a result, the spoken output mayavoid verbose, be more concise, and be more effective and informative.As another example, device 800 may receive a speech input such as “Howis the battery level on my watch and headset?” In response, device 800can provide spoken outputs using paraphrased response such as “Both at100%” or “Both could use a charge.”

In some embodiments, device 800 can generate a spoken output based oncontext information. Context information can include, for example, atotal number of electronic devices for which the status information isto be requested. In some examples, device 800 can determine whether thetotal number of the electronic devices for which the status informationis to be requested satisfies a first threshold. In accordance with adetermination that the total number of the electronic devices satisfiesthe first threshold (e.g., greater than or equal to 4), device 800 cangenerate an audio representation having a first format. An audiorepresentation having a first format, for example, may include aparaphrased response instead of listing the status information of eachelectronic device one-by-one. For example, as shown in FIG. 8F, device800 determines that the user intent is to request the status informationof all electronic devices. The context information indicates that thereare 4 devices for which the status information is to be requested (e.g.,device 800 itself such as a smartphone, watch 830, headset 840, andtablet 850). Device 800 can thus determine that the total number ofelectronic devices for which the status information is to be requestedsatisfies the first threshold (e.g., equal to 4). As a result, device800 can generate an audio representation having a first format. Forexample, spoken output 828F can include an audio representation having aparaphrase response such as “Your tablet and phone could use a charge,they're both below 30%. Your watch and your headset are both above 80%.”In some examples, device 800 can provide spoken output 828F to user 810.

With reference to FIG. 8G, in some examples, in accordance with adetermination that the total number of the electronic devices does notsatisfy the first threshold (e.g., less than 4), device 800 can generateau audio representation having a second format. An audio representationhaving a second format may not use a paraphrased response. For example,an audio representation having a second format may include a list of thestatus information of each electronic device one-by one. As shown inFIG. 8G, device 800 may determine that the user intent is to requeststatus information for all devices. The context information indicatesthat there are total of 3 devices for which the status information is tobe requested (e.g., device 800 itself such as a smartphone, watch 830,and headset 840). Device 800 can thus determine that the total number ofelectronic devices for which the status information is to be requesteddoes not satisfy the first threshold (e.g., less than 4). As a result,device 800 can generate an audio representation having a second format.For example, spoken output 828G may include an audio representation ofthe status information of each device, such as “Your phone is 28%, yourwatch is at 55%, and your headset is at 88%.” In some examples, device800 can provide spoken output 828G to user 810.

As described, in some embodiments, to request the status information ofone or more electronic devices, device 800 can identify at least oneelectronic device for which the status information is to be requested.With reference to FIG. 8H, in some embodiments, device 800 can identifythe at least one electronic device based on context information. Similarto FIG. 8F, FIG. 8H illustrates that user 810 provides a speech input824H including, for example, “Is everything charged?” Device 800 maydetermine that the user intent is, for example, to request statusinformation for all electronic devices based on the keyword “everything”included in speech input 824H. After the determination of the userintent, device 800 can identify the electronic devices for which thestatus information is to be requested. In some embodiments, theidentification of the electronic devices may be based on contextinformation. Context information can include, for example: thedetectability of one or more electronic devices and/or the availabilityof one or more electronic devices. The detectability of the electronicdevices indicates whether the electronic devices are detectable by, forexample, device 800. As shown in FIG. 8G, the Bluetooth connection ofheadset 840 may be disabled or lost, or headset 840 may be locatedbeyond a detectable range. As a result, headset 840 may not bedetectable by device 800. The availability of the electronic devicesindicates whether the electronic devices are available to respond to arequest of status information. For example, tablet 850 may be configuredto not share its location information (e.g., GPS location disabled). Asa result, tablet 850 may be unavailable to respond to a request oflocation status information.

As shown in FIG. 8H, if the context information indicates that headset840 is undetectable and/or unavailable, device 800 may identify otherelectronic devices (e.g., watch 830, tablet 850, and device 800 itselfsuch as a smartphone) in accordance with the determination that thestatus information of all devices is to be requested. Device 800communicates the request to the identified electronic devices, receivesthe status information, and generates a spoken output 828H. Spokenoutput 828G may indicate an audio representation indicating that thestatus of headset 840 is undetectable and/or unavailable. For example,the audio representation may include “Your tablet and phone could use acharge, they're both below 30%. Your watch is at 55%, and I don't seeany headset connected.” In some examples, device 800 can provide spokenoutput 828G to user 810.

As described, a speech input may include information that does notidentify at least one electronic device. In some embodiments, asdescribed above, the speech input (e.g., speech input 824C) can includeinformation without a reference identifying any specific electronicdevice (e.g., “How is the battery level?”). In some embodiments, aspeech input can include information in addition to one or morereferences identifying at least one electronic device. With reference toFIG. 8I, for example, speech input 824I can include “What are thebattery levels of my watch and other devices?” As described, the phrase“my watch” is a reference identifying a specific electronic device(e.g., watch 830). In addition to the phrase “my watch,” speech input824I also includes another phrase “other devices,” which is informationthat does not identify a specific electronic device.

As shown in FIG. 8I, in some examples, device 800 can determine the userintent based on speech input 824I. For example, device 800 can determinethe user intent based on the one or more references included in speechinput 824I (e.g., “my watch”), based on an expression included in thespeech input (e.g., the plural verb “are” and the plural noun “levels”),based on one or more keywords (e.g., “other devices”), or based on acombination therefore. In FIG. 8I, device 800 can determine that theuser intent is, for example, to request status information for alldevices including the user's watch. Based on the determination of theuser intent, device 800 can identify that the electronic devices forwhich the status information is to be requested. For example, device 800can identify watch 830, headset 840, tablet 850, and device 800 itselfsuch as a smartphone. Device 800 communicates the request to theidentified electronic devices and receives the status information fromthem. Device 800 can then generate a spoken output 828I including anaudio representation of the status information such as “Your watch is at35, headset at 92, phone at 88, and tablet at 92.” In some examples,device 800 can provide spoken output 828I to user 810.

With reference to FIG. 9A, in some embodiments, device 800 can generatea spoken output based on the type of an invoking device. As describedabove, a speech input may be received at device 800 (e.g., a smartphone)or at another device (e.g., headset 840). An invoking device receivesthe user input directly from the user. As shown in FIG. 9A, in someexamples, headset 840 can receive speech input 924A directly from user810 and thus headset 840 is the invoking device. For example, headset840 can receive speech input 924A including “How is the battery level ofmy headset?” Headset 840 can transmit speech input 924A or arepresentation thereof (e.g., an audio recording of speech input 924A)to device 800. Device 800 can determine that the user intent is torequest status information of headset 840 based on, for example, thereference identifying “my headset.” Device 800 can thus request thestatus information from headset 840 and generate spoken output 928A. Insome examples, if the invoking device is a headset (e.g., headset 840),the spoken output can include more detailed status information such asthe status of the left earbud, the status of the right earbud, thestatus of a case associated with the headset, or a combination thereof.For example, as shown in FIG. 9A, spoken output 928A can include anaudio representation of the status information such as “Your left earbudis at 35%. your right one is at 65%, and your case is at 70%.” In someexamples, device 800 can cause headset 840 to provide spoken output 928Ato user 810.

With reference to FIG. 9B, in some embodiments, if the invoking deviceis not a headset, the spoken output can include less detailed statusinformation. In FIG. 9B, user 810 may provide a speech input 924B (e.g.,“How is the battery level of my headset?”). In FIG. 9B, device 800receives speech input 924B directly from user 810 and therefore is theinvoking device. Device 800 can determine that the user intent is torequest status information of headset 840 based on, for example, thereference identifying “my headset.” Device 800 can thus request thestatus information from headset 840 and generate spoken output 928B. Insome examples, if the invoking device is a device other than a headset,the spoken output can include less detailed status information (e.g., anoverall status of the headset). For example, as shown in FIG. 9B, spokenoutput 928B can include an audio representation of the statusinformation such as “Your earbuds are at 55%.” In some examples, device800 can provide spoken output 928B to user 810.

With references to FIGS. 10A-10D, in some embodiments, device 800 cangenerate the spoken output based on the status information received fromthe electronic devices. As described, the status information of one ormore of the electronic devices can include at least one of batterystatus information, connectivity status information, operating modestatus information, location status information, device configurationstatus information, or the like. As shown in FIGS. 10A-10D, device 800can receive a speech input 1024 such as “How is my battery level on mywatch?” Based on speech input 1024, device 800 can determine that theuser intent is to request the battery status information of the user'swatch. Device 800 can request the battery status information of watch1030 and generate spoken output 1028A-1028D based on the battery statusinformation received from watch 1030. Spoken output 1028A-1028D mayinclude different audio representations of different battery statusinformation of watch 1030.

As illustrated in FIG. 10A, the battery status information that device800 received may indicate that the battery level is at 100 percent.Accordingly, device 800 may generate spoken output 1028A including anaudio representation of the battery status information such as “It's at100%, perfect score!” As illustrated in FIG. 10B, the battery statusinformation device 800 received may indicate that the battery level ofwatch 1030 is at 90 percent. Accordingly, device 800 may generate spokenoutput 1028A including an audio representation of the battery statusinformation such as “You're juiced up and ready to go! It's at 90%.” Asillustrated in FIG. 10C, the battery status information device 800received may indicate that the battery level of watch 1030 is at 5percent. Accordingly, device 800 may generate spoken output 1028Cincluding an audio representation of the battery status information suchas “It's at 5%. May the charge be with you.” As illustrated in FIG. 10D,the status information that device 800 received may indicate that thebattery level of watch 1030 is at 1 percent. Accordingly, device 800 maygenerate spoken output 1028D including an audio representation of thebattery status information such as “You only have 1 percent left. Well,[pause] it was nice talking with you.” It is appreciated that batterylevels indicated in FIGS. 10A-10D are examples and device 800 cangenerate different spoken output based on various status information(e.g., different battery percentages).

With reference to FIG. 10E, in some embodiments, device 800 can generatea spoken output based on a determination of whether the statusinformation satisfies a second threshold. As shown in FIG. 10E, device800 can receive a speech input 1036 including, for example, “Iseverything charged?” Based on speech input 1036, device 800 candetermine that the user intent is to request the status information ofthe all electronic devices. Device 800 can request the statusinformation of all electronic devices and generate spoken output 1038based on the status information received from each of the electronicdevice. For example, the status information received from watch 830 andheadset 840 may indicate that their battery levels are above 80%. Thestatus information received from tablet 850 and device 800 itself (e.g.,a smartphone) may indicate that their battery levels are below 30%. Insome examples, the second threshold can be a threshold percentage of theremaining battery level of an electronic device. For example, the secondthreshold may be 30%. Using the second threshold, device 800 candetermine the status information of tablet 850 and device 800 satisfiesthe second threshold (e.g., the remaining battery levels of tablet 850and device 800 are both below the second threshold of 30%). As a result,device 800 can include an audio representation of the status informationof tablet 850 and device 800 in the spoken output 1038. Further, device800 can determine the status information of watch 830 and headset 840does not satisfy the second threshold (e.g., the remaining batterylevels of watch 830 and headset 840 are both above the second thresholdof 30%). As a result, in some examples, device 800 can exclude an audiorepresentation of the status information of watch 830 and headset 840from spoken output 1038. In some examples, device 800 can include anaudio representation of substitute information in spoken output 1038 inlieu of the status information of watch 830 and headset 840. As shown inFIG. 10E, spoken output 1038 can include, for example, “Your tablet andphone could use a charge, they're both below 30%. Everything else looksgood.”

5. Process for Providing a Spoken Output Representing StatusInformation.

FIGS. 11A-11F illustrate a flow diagram of an exemplary process 1100 foroperating a digital assistant in accordance with some embodiments.Process 1100 may be performed using one or more devices 104, 108, 200,400, 600, or 800, (FIG. 1, 2A, 4, 6A-B, 8A-8I, 9A-9B, or 10A-10E).Operations in process 1100 are, optionally, combined or split and/or theorder of some operations is, optionally, changed.

With reference to FIG. 11A, at block 1102, a speech input is received.At block 1104, the speech input is received from a user at an invokingdevice. The invoking device may include a user device or an electronicdevice that is communicatively connected to the user device. The userdevice is operable to communicate with one or more electronic devices.

At block 1106, a user intent is determined based on the speech input. Atblock 1107, text is generated based on the speech input. At block 1109,natural language processing is performed on the text. At block 1110, theuser intent is determined based on a result of the natural languageprocess.

At block 1112, it is determined whether the speech input includes one ormore references identifying at least one of the one or more electronicdevices. At block 1113, the speech input includes information inaddition to the one or more references identifying at least one of theone or more electronic devices. At block 1115, the speech input includesinformation without a reference identifying at least one of the one ormore electronic devices.

At block 1116, in accordance with a determination that the speech inputincludes one or more references identifying at least one of the one ormore electronic devices, the user intent is determined based on the oneor more references.

With reference to FIG. 11B, at block 1118, in accordance with adetermination that the speech input includes information that does notidentify at least one of the one or more electronic devices, the userintent is determined based on at least one of an expression of thespeech input or one or more keywords included in the speech input.

At block 1120, it is determined whether the speech input includes asingular form expression or a plural form expression. At block 1122, inaccordance with a determination that the speech input includes asingular form expression, it is determined, from the one or moreelectronic devices, a single electronic device for which statusinformation is to be requested. At block 1123, the single electronicdevice for which the status information is to be requested includes aninvoking device. The invoking device receives the speech input from theuser.

At block 1124, in accordance with a determination that the speech inputincludes a plural form expression, it is determined, from the one ormore electronic devices, at least two electronic devices for whichstatus information is to be requested. At block 1126, the at least twoelectronic devices for which the status information is to be requestedincludes an invoking device. The invoking device receives the speechinput from the user.

With reference to FIG. 11C, at block 1128, it is determined whether thespeech input includes one or more keywords. At block 1130, in accordancewith a determination that the speech input includes one or morekeywords, it is determined, from the one or more electronic devices, atleast one electronic device for which status information is to berequested. At block 1132, the at least one electronic device for whichthe status information is to be requested includes an invoking device.The invoking device receives the speech input from the user.

At block 1134, in accordance with the user intent, status informationassociated with at least one of the one or more electronic devices isrequested. At block 1135, the status information associated with the atleast one of the one or more electronic devices includes at least one ofbattery status information, connectivity status information, operatingmode status information, location status information, or deviceconfiguration status information.

At block 1136, based on the determination of the user intent, the atleast one of the one or more electronic devices for which the statusinformation is to be requested is identified. At block 1137, identifyingthe at least one of the one or more electronic devices for which thestatus information is to be requested is further based on contextinformation. The context information indicates at least one ofdetectability of the one or more electronic devices or availability ofthe one or more electronic devices. At block 1138, a request for thestatus information is communicated to the at least one of the one ormore electronic devices for which the status information is to berequested.

With reference to FIG. 11D, at block 1140, the status informationassociated with the at least one of the one or more electronic devicesis received. At block 1142, the status information includes batterystatus of a headset communicatively connected to the user device. Atblock 1143, receiving the status information associated with the atleast one of the one or more electronic devices includes receiving atleast one of: overall battery status of the headset, battery status of aleft earbud and a right earbud of the headset, and battery status of acase associated with the headset.

At block 1144, a spoken output representing the status informationassociated with the at least one of the one or more electronic devicesis generated. At block 1146, the spoken output is generated in an orderthat corresponds to an order of the one or more references identifyingthe at least one of the one or more electronic devices in the speechinput. At block 1148, the spoken output is generated using a paraphrasedresponse.

At block 1150, the spoken output is generated based on a type of aninvoking device. The invoking device receives the speech input from theuser. At block 1152, the invoking device is a headset and generating thespoken output based on the type of the invoking device comprisesgenerating the an audio representation of at least one of: overallbattery status of the headset, battery statuses of a left earbud and aright earbud of the headset, and battery status of a case associatedwith the headset.

With reference to FIG. 11E, at block 1154, the spoken output isgenerated based on context information. At block 1156, it is determinedwhether a total number of the at least one of the one or more electronicdevices satisfies a first threshold. At block 1158, in accordance with adetermination that the total number of the at least one of the one ormore electronic devices satisfies the first threshold, an audiorepresentation having a first format is generated. At block 1160, inaccordance with a determination that the total number of the at leastone of the one or more electronic devices does not satisfy the firstthreshold, an audio representation having a second format is generated.

At block 1162, the spoken output is generated based on the statusinformation associated with the at least one of the one or moreelectronic devices. At block 1164, it is determined, for each of the atleast one of the one or more electronic devices, whether the statusinformation satisfies a second threshold. At block 1166, in accordancewith a determination that the status information satisfies the secondthreshold, an audio representation of the status information associatedwith at least one of the one or more electronic devices is included. Atblock 1168, in accordance with a determination that the statusinformation does not satisfy the second threshold, at least one of thefollowing is performed: excluding the audio representation of the statusinformation associated with the at least one of the one or moreelectronic devices, and including an audio representation of substituteinformation in lieu of the status information.

With reference to FIG. 11F, at block 1170, the spoken output isgenerated according to battery status information associated with the atleast one of the one or more electronic devices.

At block 1174, the spoken output is caused to be provided to the user.At block 1176, the spoken output is caused to be provided to the user atthe user device. At block 1178, the spoken output is caused to beprovided to the user at an electronic device communicatively connectedto the user device.

6. Electronic Device

FIG. 12 shows a functional block diagram of electronic device 1200configured in accordance with the principles of the various describedexamples, including those described with reference to FIGS. 8A-8I,9A-9B, and 10A-10E. The functional blocks of the device can beoptionally implemented by hardware, software, or a combination ofhardware and software to carry out the principles of the variousdescribed examples. It is understood by persons of skill in the art thatthe functional blocks described in FIG. 12 can be optionally combined orseparated into sub-blocks to implement the principles of the variousdescribed examples. Therefore, the description herein optionallysupports any possible combination, separation, or further definition ofthe functional blocks described herein.

As shown in FIG. 12, electronic device 1200 can include a microphone1202 and processing unit 1208. In some examples, processing unit 1208includes a receiving unit 1210, a determining unit 1212, a generatingunit 1214, a performing unit 1216, a requesting unit 1218, a causingunit 1220, and optionally, an identifying unit 1222, a communicatingunit 1224, an including unit 1226, and an excluding unit 1228.

In some examples, the processing unit 1208 is configured to receive(e.g., with the receiving unit 1210) a speech input; and determine(e.g., with the determining unit 1212) a user intent based on the speechinput. Determining the user intent includes generating (e.g., with thegenerating unit 1214) text based on the speech input, performing (e.g.,with the performing unit 1216) natural language processing of the text,and determining (e.g., with the determining unit 1212) the user intentbased on a result of the natural language processing.

In some examples, the processing unit 1208 is further configured torequest (e.g., with the requesting unit 1218), in accordance with theuser intent, status information associated with at least one of the oneor more electronic devices; receive (e.g., with the receiving unit 1210)the status information associated with the at least one of the one ormore electronic devices; generate (e.g., with the generating unit 1214)a spoken output representing the status information associated with theat least one of the one or more electronic devices; and cause (e.g.,with the causing unit 1220) the spoken output to be provided to theuser.

In some examples, the status information associated with the at leastone of the one or more electronic devices includes at least one ofbattery status information, connectivity status information, operatingmode status information, location status information, or deviceconfiguration status information.

In some examples, receiving a speech input includes receiving (e.g.,with the receiving unit 1210) the speech input at an invoking devicefrom a user. The invoking device includes the user device or anelectronic device that is communicatively connected to the user device.

In some examples, determining the user intent includes determining(e.g., with the determining unit 1212) whether the speech input includesone or more references identifying at least one of the one or moreelectronic devices.

In some examples, in accordance with a determination that the speechinput includes one or more references identifying at least one of theone or more electronic devices, the processing unit 1208 is configuredto determine (e.g., with the determining unit 1212) the user intentbased on the one or more references.

In some examples, in accordance with a determination that the speechinput includes information that does not identify at least one of theone or more electronic devices, the processing unit 1208 is configuredto determine (e.g., with the determining unit 1212) the user intentbased on at least one of an expression of the speech input or one ormore keywords included in the speech input.

In some examples, the speech input includes the information in additionto the one or more references identifying at least one of the one ormore electronic devices.

In some examples, the speech input includes the information without areference identifying at least one of the one or more electronicdevices.

In some examples, determining the user intent based on at least one ofan expression of the speech input or one or more keywords included inthe speech input includes determining (e.g., with the determining unit1212) whether the speech input includes a singular form expression or aplural form expression.

In some examples, in accordance with a determination that the speechinput includes a singular form expression, the processing unit 1208 isconfigured to determine, from the one or more electronic devices, asingle electronic device for which status information is to berequested.

In some examples, in accordance with a determination that the speechinput includes a plural form expression, the processing unit 1208 isconfigured to determine, from the one or more electronic devices, atleast two electronic devices for which status information is to berequested.

In some examples, the single electronic device for which the statusinformation is to be requested includes an invoking device. The invokingdevice receives the speech input from the user.

In some examples, the at least two electronic devices for which thestatus information is to be requested includes an invoking device. Theinvoking device receives the speech input from the user.

In some examples, determining the user intent based on at least one ofan expression of the speech input or one or more keywords included inthe speech input includes determining (e.g., with the determining unit1212) whether the speech input includes one or more keywords.

In some examples, in accordance with a determination that the speechinput includes one or more keywords, the processing unit 1208 isconfigured to determine ((e.g., with the determining unit 1212), fromthe one or more electronic devices, at least one electronic device forwhich status information is to be requested.

In some examples, the at least one electronic device for which thestatus information is to be requested includes an invoking device. Theinvoking device receives the speech input from the user.

In some examples, requesting status information associated with the atleast one of the one or more electronic devices includes identifying(e.g., with the identifying unit 1222), based on the determination ofthe user intent, the at least one of the one or more electronic devicesfor which the status information is to be requested; and communicating(e.g., with the communicating unit 1224) a request for the statusinformation to the at least one of the one or more electronic devicesfor which the status information is to be requested.

In some examples, identifying the at least one of the one or moreelectronic devices for which the status information is to be requestedis further based on context information. The context informationindicates at least one of detectability of the one or more electronicdevices or availability of the one or more electronic devices.

In some examples, the status information includes battery status of aheadset communicatively connected to the user device.

In some examples, receiving the status information associated with theat least one of the one or more electronic devices includes receiving atleast one of: overall battery status of the headset, battery status of aleft earbud and a right earbud of the headset, and battery status of acase associated with the headset.

In some examples, generating the spoken output representing the statusinformation associated with the at least one of the one or moreelectronic devices includes generating (e.g., with the generating unit1214) the spoken output in an order that corresponds to an order of theone or more references identifying the at least one of the one or moreelectronic devices in the speech input.

In some examples, generating the spoken output representing the statusinformation associated with the at least one of the one or moreelectronic devices includes generating (e.g., with the generating unit1214) the spoken output using a paraphrased response.

In some examples, generating the spoken output representing the statusinformation associated with the at least one of the one or moreelectronic devices includes generating (e.g., with the generating unit1214) the spoken output based on a type of an invoking device. Theinvoking device receives the speech input from the user.

In some examples, generating the spoken output representing the statusinformation associated with the at least one of the one or moreelectronic devices includes generating (e.g., with the generating unit1214) the spoken output based on context information.

In some examples, generating the spoken output representing the statusinformation associated with the at least one of the one or moreelectronic devices includes generating (e.g., with the generating unit1214) the spoken output based on the status information associated withthe at least one of the one or more electronic devices.

In some examples, the invoking device is a headset. Generating thespoken output based on the type of the invoking device includesgenerating (e.g., with the generating unit 1214) an audio representationof at least one of: overall battery status of the headset, batterystatuses of a left earbud and a right earbud of the headset, and batterystatus of a case associated with the headset.

In some examples, generating the spoken output based on contextinformation includes determining (e.g., with the determining unit 1212)whether a total number of the at least one of the one or more electronicdevices satisfies a first threshold.

In some examples, in accordance with a determination that the totalnumber of the at least one of the one or more electronic devicessatisfies the first threshold, the processing unit 1208 is configured togenerate (e.g., with the generating unit 1214) an audio representationhaving a first format.

In some examples, in accordance with a determination that the totalnumber of the at least one of the one or more electronic devices doesnot satisfy the first threshold, the processing unit 1208 is configuredto generate an audio representation having a second format.

In some examples, generating the spoken output based on the statusinformation associated with the at least one of the one or moreelectronic devices includes determining (e.g., with the determining unit1212), for each of the at least one of the one or more electronicdevices, whether the status information satisfies a second threshold.

In some examples, in accordance with a determination that the statusinformation satisfies the second threshold, the processing unit 1208 isconfigured to include (e.g., with an including unit 1226) an audiorepresentation of the status information associated with at least one ofthe one or more electronic devices.

In some examples, in accordance with a determination that the statusinformation does not satisfy the second threshold, the processing unit1208 is further configured to perform (e.g., with the performing unit1216) at least one of: excluding (e.g., with the excluding unit 1228)the audio representation of the status information associated with theat least one of the one or more electronic devices, and including (e.g.,with the including unit 1226) an audio representation of substituteinformation in lieu of the status information.

In some examples, generating the spoken output based on statusinformation associated with the at least one of the one or moreelectronic devices includes: generating (e.g., with the generating unit1214) the spoken output according to battery status informationassociated with the at least one of the one or more electronic devices.

In some examples, causing the spoken output to be provided to the userincludes causing (e.g., with the causing unit 1220) the spoken output tobe provided to the user at the user device.

In some examples, causing the spoken output to be provided to the userincludes causing (e.g., with the causing unit 1220) the spoken output tobe provided to the user at an electronic device communicativelyconnected to the user device.

The operation described above with respect to FIG. 12 is, optionally,implemented by components depicted in FIG. 1, 2A, 4, 6A-B, or 7A-7B. Forexample, receiving operation 1210, determining operation 1212,generating operation 1214, and performing operation 1216 are optionallyimplemented by processor(s) 220. It would be clear to a person ofordinary skill in the art how other processes can be implemented basedon the components depicted in FIG. 1, 2A, 4, 6A-B, or 7A-7B.

It is understood by persons of skill in the art that the functionalblocks described in FIG. 12 are, optionally, combined or separated intosub-blocks to implement the principles of the various describedembodiments. Therefore, the description herein optionally supports anypossible combination or separation or further definition of thefunctional blocks described herein. For example, processing unit 1208can have an associated “controller” unit that is operatively coupledwith processing unit 1208 to enable operation. This controller unit isnot separately illustrated in FIG. 12 but is understood to be within thegrasp of one of ordinary skill in the art who is designing a devicehaving a processing unit 1208, such as device 1200. As another example,one or more units, such as the receiving unit 1210, may be hardwareunits outside of processing unit 1208 in some embodiments. Thedescription herein thus optionally supports combination, separation,and/or further definition of the functional blocks described herein.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

1. A user device, the user device being operable to communicate with oneor more electronic devices, comprising: one or more processors; memory;and one or more programs stored in memory, the one or more programsincluding instructions for: receiving a speech input; determining a userintent based on the speech input, wherein determining the user intentcomprises: generating text based on the speech input, performing naturallanguage processing of the text, and determining the user intent basedon a result of the natural language processing; requesting, inaccordance with the user intent, status information associated with atleast one of the one or more electronic devices; receiving the statusinformation associated with the at least one of the one or moreelectronic devices; generating a spoken output representing the statusinformation associated with the at least one of the one or moreelectronic devices; and causing the spoken output to be provided to theuser.
 2. The user device of claim 1, wherein the status informationassociated with the at least one of the one or more electronic devicesincludes at least one of battery status information, connectivity statusinformation, operating mode status information, location statusinformation, or device configuration status information.
 3. The userdevice of claim 1, wherein receiving a speech input comprises: receivingthe speech input at an invoking device from a user, wherein the invokingdevice includes the user device or an electronic device that iscommunicatively connected to the user device.
 4. The user device ofclaim 1, wherein determining the user intent comprises: determiningwhether the speech input includes one or more references identifying atleast one of the one or more electronic devices; in accordance with adetermination that the speech input includes one or more referencesidentifying at least one of the one or more electronic devices,determining the user intent based on the one or more references; and inaccordance with a determination that the speech input includesinformation that does not identify at least one of the one or moreelectronic devices, determining the user intent based on at least one ofan expression of the speech input or one or more keywords included inthe speech input.
 5. The user device of claim 4, wherein the speechinput includes the information in addition to the one or more referencesidentifying at least one of the one or more electronic devices.
 6. Theuser device of claim 4, wherein the speech input includes theinformation without a reference identifying at least one of the one ormore electronic devices.
 7. The user device of claim 4, whereindetermining the user intent based on at least one of an expression ofthe speech input or one or more keywords included in the speech inputcomprises: determining whether the speech input includes a singular formexpression or a plural form expression; in accordance with adetermination that the speech input includes a singular form expression,determining, from the one or more electronic devices, a singleelectronic device for which status information is to be requested; andin accordance with a determination that the speech input includes aplural form expression, determining, from the one or more electronicdevices, at least two electronic devices for which status information isto be requested.
 8. The user device of claim 7, wherein the singleelectronic device for which the status information is to be requestedincludes an invoking device, wherein the invoking device receives thespeech input from the user.
 9. The user device of claim 7, wherein theat least two electronic devices for which the status information is tobe requested includes an invoking device, wherein the invoking devicereceives the speech input from the user.
 10. The user device of claim 4,wherein determining the user intent based on at least one of anexpression of the speech input or one or more keywords included in thespeech input comprises: determining whether the speech input includesone or more keywords; and in accordance with a determination that thespeech input includes one or more keywords, determining, from the one ormore electronic devices, at least one electronic device for which statusinformation is to be requested.
 11. The user device of claim 10, whereinthe at least one electronic device for which the status information isto be requested includes an invoking device, wherein the invoking devicereceives the speech input from the user.
 12. The user device of claim 1,wherein requesting status information associated with the at least oneof the one or more electronic devices comprises: identifying, based onthe determination of the user intent, the at least one of the one ormore electronic devices for which the status information is to berequested; and communicating a request for the status information to theat least one of the one or more electronic devices for which the statusinformation is to be requested.
 13. The user device of claim 12, whereinidentifying the at least one of the one or more electronic devices forwhich the status information is to be requested is further based oncontext information, wherein the context information indicates at leastone of detectability of the one or more electronic devices oravailability of the one or more electronic devices.
 14. The user deviceof claim 1, wherein the status information includes battery status of aheadset communicatively connected to the user device.
 15. The userdevice of claim 14, wherein receiving the status information associatedwith the at least one of the one or more electronic devices comprisesreceiving at least one of: overall battery status of the headset,battery status of a left earbud and a right earbud of the headset, andbattery status of a case associated with the headset.
 16. The userdevice of claim 1, wherein generating the spoken output representing thestatus information associated with the at least one of the one or moreelectronic devices comprises at least one of: generating the spokenoutput in an order that corresponds to an order of the one or morereferences identifying the at least one of the one or more electronicdevices in the speech input; generating the spoken output using aparaphrased response; generating the spoken output based on a type of aninvoking device, wherein the invoking device receives the speech inputfrom the user; generating the spoken output based on contextinformation; and generating the spoken output based on the statusinformation associated with the at least one of the one or moreelectronic devices.
 17. The user device of claim 16, wherein theinvoking device is a headset and wherein generating the spoken outputbased on the type of the invoking device comprises generating the anaudio representation of at least one of: overall battery status of theheadset, battery statuses of a left earbud and a right earbud of theheadset, and battery status of a case associated with the headset. 18.The user device of claim 16, wherein generating the spoken output basedon context information comprises: determining whether a total number ofthe at least one of the one or more electronic devices satisfies a firstthreshold; in accordance with a determination that the total number ofthe at least one of the one or more electronic devices satisfies thefirst threshold, generating an audio representation having a firstformat; and in accordance with a determination that the total number ofthe at least one of the one or more electronic devices does not satisfythe first threshold, generating an audio representation having a secondformat.
 19. The user device of claim 16, wherein generating the spokenoutput based on the status information associated with the at least oneof the one or more electronic devices comprises: determining, for eachof the at least one of the one or more electronic devices, whether thestatus information satisfies a second threshold; in accordance with adetermination that the status information satisfies the secondthreshold, including an audio representation of the status informationassociated with at least one of the one or more electronic devices; andin accordance with a determination that the status information does notsatisfy the second threshold, performing at least one of: excluding theaudio representation of the status information associated with the atleast one of the one or more electronic devices, and including an audiorepresentation of substitute information in lieu of the statusinformation.
 20. The user device of claim 16, wherein generating thespoken output based on status information associated with the at leastone of the one or more electronic devices comprises: generating thespoken output according to battery status information associated withthe at least one of the one or more electronic devices.
 21. The userdevice of claim 1, wherein causing the spoken output to be provided tothe user comprises: causing the spoken output to be provided to the userat the user device.
 22. The user device of claim 1, wherein causing thespoken output to be provided to the user comprises: causing the spokenoutput to be provided to the user at an electronic devicecommunicatively connected to the user device.
 23. A non-transitorycomputer-readable storage medium comprising one or more programs forexecution by one or more processors of a user device, the user devicebeing operable to communicate with one or more electronic devices, theone or more programs including instructions which, when executed by theone or more processors, cause the user device to: receive a speechinput; determine a user intent based on the speech input, whereindetermining the user intent comprises: generating text based on thespeech input, performing natural language processing of the text, anddetermining the user intent based on a result of the natural languageprocessing; request, in accordance with the user intent, statusinformation associated with at least one of the one or more electronicdevices; receive the status information associated with the at least oneof the one or more electronic devices; generate a spoken outputrepresenting the status information associated with the at least one ofthe one or more electronic devices; and cause the spoken output to beprovided to the user.
 24. A method for operating a digital assistant,comprising: at a user device with one or more processors and memory, theuser device operable to communicate with one or more electronic devices:receiving a speech input; determining a user intent based on the speechinput, wherein determining the user intent comprises: generating textbased on the speech input, performing natural language processing of thetext, and determining the user intent based on a result of the naturallanguage processing; requesting, in accordance with the user intent,status information associated with at least one of the one or moreelectronic devices; receiving the status information associated with theat least one of the one or more electronic devices; generating a spokenoutput representing the status information associated with the at leastone of the one or more electronic devices; and causing the spoken outputto be provided to the user.